No WWW-Authenticate header sent when error-page 401 is configured

[Nick Wiedenbrück <ma...@googlemail.com>]

Hi, I'm trying to get digest authentication working on Tomcat 5.5.23. I got
it working on Tomcat 6 and Jetty, but I've got a problem with Tomcat 5.5.23,
because there no WWW-Authenticate header is sent. I figured out that it will
work if I remove error-page 401 configuration from my web.xml. What's the
reason?

Regards,
Nick

Re: No WWW-Authenticate header sent when error-page 401 is configured

[Konstantin Kolinko <kn...@gmail.com>]

2010/3/30 Nick Wiedenbrück <ma...@googlemail.com>:
> I got it working on Tomcat 6 and Jetty, but I've got a problem with Tomcat 5.5.23,

It will not work with 5.5.23, because it is some issue that was fixed
in a later version. (Headers were cleared when rendering a custom
page). Search the bugzilla or look in the changelog.

I am certain that it is fixed in 6.0.x about a year ago, but I do not
remember whether it was backported to 5.5 or not -- you can find that
yourself (e.g. try 5.5.28).

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org