https://bz.apache.org/bugzilla/show_bug.cgi?id=57629
--- Comment #5 from Mark Thomas ---
Yes. You get the right 4xx response along with a Connection: close header.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57629
--- Comment #4 from Christopher Schultz ---
Does this currently work when Tomcat /is/ managing the authentication and
authorization? If so, then I agree with WONTFIX.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57629
Mark Thomas changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=57629
--- Comment #2 from Lorenzo Caenazzo ---
ok,
I think the responability to send 100-continue header is not of "contained"
application.
But if the container send a 100 header I expect which it not closes the soket
if the body of the request is "
https://bz.apache.org/bugzilla/show_bug.cgi?id=57629
--- Comment #1 from Mark Thomas ---
This is only going to work if Tomcat does the authentication otherwise, as you
have observed, Tomcat sends the 100 response before passing the
request/response to the application for processing.
One of the a
