On 21/11/17 16:53, Christopher Schultz wrote: > Mark, > > On 11/20/17 3:03 PM, ma...@apache.org wrote: >> Author: markt Date: Mon Nov 20 20:03:34 2017 New Revision: 1815840 > >> URL: http://svn.apache.org/viewvc?rev=1815840&view=rev Log: Revert >> accidental commit > >> Modified: tomcat/trunk/conf/jaspic-providers.xml > >> Modified: tomcat/trunk/conf/jaspic-providers.xml URL: >> http://svn.apache.org/viewvc/tomcat/trunk/conf/jaspic-providers.xml?re > v=1815840&r1=1815839&r2=1815840&view=diff > > > ======================================================================== > ====== >> --- tomcat/trunk/conf/jaspic-providers.xml (original) +++ >> tomcat/trunk/conf/jaspic-providers.xml Mon Nov 20 20:03:34 2017 @@ >> -1,9 +1,23 @@ -<?xml version='1.0' encoding='utf-8'?> >> -<jaspic-providers - xmlns="http://tomcat.apache.org/xml"; - >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; - >> xsi:schemaLocation="http://tomcat.apache.org/xml >> jaspic-providers.xsd" > > Looks like the schemaLocation returns a 404 response. Do we expect that > there is a .xsd file actually available there?
Not at the moment. > I think that URL should respond, possibly with a long pause a la > w3.org's behavior when you request standard XML resources from their > canonical locations. Not sure how easy that would be to implement. What is the impact of continuing to return a 404? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
