-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shilpa,
Shilpa Arora wrote: > We also tried another thing. Our *web.xml* was for a Struts application, > so we had following tags in it. > > <taglib> > <taglib-uri>/tags/struts-html</taglib-uri> > <taglib-location>/WEB-INF/struts-html.tld</taglib-location> > </taglib> > > We commented out all such tags and the application worked fine i.e. it > prompted us for the login and we were able to see *about.html*. > > But for our struts application we need these *taglib *tags. So, does it > mean, this BASIC authentication is not compatible with struts? Or is > there some alternative way of specifying things for Struts. This really shouldn't be a problem, but you can create another <security-constraint> with no <auth-constraint> but contains your tld files. This will prevent the authorization from failing when looking for that file. But, the JSP compiler should be handling that file, not any part of Tomcat that determines if it is okay to access that particular resource when a request is made. I think your problem might be somewhere else. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFsSps9CaO5/Lv0PARAoUKAJ9DTNpv+3mChBhVHbrr5YjuGP01jwCeNwBV q6OWdz0Sdk6kQeV+4hzJ0kM= =FuOE -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]