[I don't know why, looks like the original message didn't make it to
the list... Sorry if it's a double send]
Hello,
As the subject says, we have a problem with Tomcat 5.0 (5.0.27 through
5.0.30 to be precise) where a servlet invoked from tomcat5 does NOT
send a www-authenticate header back, resulting in a definitive 401
error. This violates RFC 2616 (paragraph 14.47).
As we suspected Apache first, I shut it down, activated the Coyote
HTTP/1.1 connector of Tomcat, pointed the web browser to the 8080 port
of the machine... But the result is the same. It occurs regardless of
the presence of a proxy inbetween or not FWIW.
The biggest problem is that I don't have the slightest idea at where
to start... Only thing is I can show these exerpts from the
WEB-INF/web.xml of our webapp:
------
<servlet>
<servlet-name>content</servlet-name>
<servlet-class>com.one2team.one2web.repository.ShowDocumentContent</servlet-class>
</servlet>
[...]
<servlet-mapping>
<servlet-name>content</servlet-name>
<url-pattern>/servlet/ShowDocumentContent</url-pattern>
</servlet-mapping>
------
And that's it, really...
Any ideas? I've long run short of them myself :(
Merry Christmas BTW, and thanks in advance for your help,
--
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
--
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]
