Hello, Our webapp runs with Tomcat 5, Apache 2.0.46 from RHEL3, Tomcat 5.0.27 from JPackage, and communicate via mod_jk 1.2.6.
Here's the problem we face: our webapp sends notifications by email, with a link to a JSP requiring a classical HTTP authentication dialog. This same page is used for the login form into the application, and its behaviour is controlled by the parameters passed to it. When the user DOES NOT submit any information (ie, it presses "Cancel" on the dialog box), Tomcat shows its 401 page. I've tried the following: * add an ErrorDocument directive to Apache config: no go; * add an <error-page> tag with <error-code> and <location> into the <web-app> section of WEB-INF/web.xml with the location pointing back to the same page, with no parameters: no go either... It's even worse in this case, since the Tomcat 401 page shows directly, the HTTP auth dialog doesn't even appear. I haven't tried _both_ at the same time, but I believe it wouldn't be the solution. As I'm not really fluent with Apache/Tomcat and webapps, I don't know where I should look at to solve the problem. Any hints would be more than welcome! Thanks for reading, and it'd be nice to reply-all, since the two CC are not on the list, -- Francis Galiegue, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] One2team - 12bis rue de la Pierre Levée, 75011 Paris - 0143381980 "When it comes to performance, weight is everything" - Tiff Needell --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
