You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/06 20:00:52 UTC

DO NOT REPLY [Bug 31567] - 505 request error from .NET client

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31567>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31567

505 request error  from .NET client

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From remm@apache.org  2004-10-06 18:00 -------
- Capture the exact request bytes
- Open a telnet 127.0.0.1 8080 (with the default config)
- Send the bytes
If it still breaks, attach the said bytes to the bug report as a file, so that I
can reproduce it.

My understanding of the issue is that this your client is broken: it requires an
expectation, which is not fulfilled (401), but sends the request body anyway
(lol). Tomcat will use your request body as the first line of the next request,
and then of course send a 505.

Solution if my theory is correct: add the user-agent as a restricted user agent
so that keep alive isn't used (or disable keep alive).

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