tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31567] - 505 request error from .NET client
Date Fri, 19 Nov 2004 15:52:11 GMT
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


per.thornstrand@omxgroup.com changed:

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




------- Additional Comments From per.thornstrand@omxgroup.com  2004-11-19 16:52 -------
I'm no expert at HTTP, but shouldn't Tomcat drop the TCP-connection after 
having sent the initial "401 Unauthorized"-resonse? 

This would cause .NET to do its re-post (with included authorization data in 
the HTTP Header) in a new TCP connection. 

In other words Tomcat should not use keep alive after a 401 Unauthorized. I 
think this is how IIS (and Tomcat 4.x i suspect) behaves. 


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message