https://issues.apache.org/bugzilla/show_bug.cgi?id=57324
Vamsi Krishna <vkris...@novell.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #6 from Vamsi Krishna <vkris...@novell.com> ---
Mark,
I have upgraded to Tomcat 7.0.57 and the problem is still reproducible. I have
attached the screenshot of my wireshark trace which clearly demonstrates a
connection closure after a 401 response from Tomcat. Note that Tomcat 7.0.39
does not have this behavior.
In the trace, you will find the packets highlighted in red that demonstrates
the connection closure from Tomcat.
I have also checked the code and in AbstractHttp11Processor from Tomcat 7.0.57,
I do not see any different handling for 401
**************************Snippet *****************************
if (!isAsync() && !comet) {
if (getErrorState().isError()) {
// If we know we are closing the connection, don't drain
// input. This way uploading a 100GB file doesn't tie up
the
// thread if the servlet has rejected it.
getInputBuffer().setSwallowInput(false);
} else if (expectation &&
(response.getStatus() < 200 || response.getStatus() >
299)) {
// Client sent Expect: 100-continue but received a
// non-2xx final response. Disable keep-alive (if enabled)
// to ensure that the connection is closed. Some clients
may
// still send the body, some may send the next request.
// No way to differentiate, so close the connection to
// force the client to send the next request.
getInputBuffer().setSwallowInput(false);
keepAlive = false;
}
endRequest();
}
****************************End of Snippet **************************
Let me know what is missing link here ?
Thanks for your time.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
