Message 4954 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	kyrrigle
Date	2002年03月28日.20:49:53
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=247536 it appears that IE is sending 2 extra bytes ('\r\n') after the request data. and if you don't read those two extra bytes off, the window's socket handling gets messed up. the result is that a partial response is returned and the socket closed. IE tries to recover by re-POST'ing (which is behavior specified in the HTTP/1.1 RFC)... only they seem to add an embedded NULL the second time through, and the original socket problem happens again anyway. Try reading an extra 2 bytes from the rfile before sending your response and the problem should go away. not sure what the real fix for this should be?

Content

Logged In: YES 
user_id=247536
it appears that IE is sending 2 extra bytes ('\r\n') after 
the request data. and if you don't read those two extra 
bytes off, the window's socket handling gets messed up.
the result is that a partial response is returned and the 
socket closed. IE tries to recover by re-POST'ing (which 
is behavior specified in the HTTP/1.1 RFC)... only they 
seem to add an embedded NULL the second time through, and 
the original socket problem happens again anyway.
Try reading an extra 2 bytes from the rfile before sending 
your response and the problem should go away.
not sure what the real fix for this should be?

History
Date	User	Action	Args
2007年08月23日 13:54:42	admin	link	issue430160 messages
2007年08月23日 13:54:42	admin	create

homepage