➜
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.
Created on 2008-02-16 13:16 by juneaftn, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg62455 - (view) | Author: June Kim (juneaftn) | Date: 2008-02-16 13:18 | |
http://bugs.python.org/issue430160 http://bugs.python.org/issue427345 These two issues refer to the same bug, which occurs when there is a POST from an Internet Explorer and the POST's content is long enough. The issue was resolved by changing the CGIHTTPServer.py to consume the remaining garbage. However, the bug potentially remains with BaseHTTPServer.py(and hence its descendants like SimpleHTTPServer, and 3rd party libraries like MoinMoin's stand alone server). People should have the knowledge of the IE POST bug and put the code for treating it everytime when they use BaseHTTPServer. Simple way to solve this is inserting the garbage consuming code in the "finish" method: while select.select([self.rfile], [],[],0)[0]: if not self.rfile.read(1): break |
|||
| msg64107 - (view) | Author: Sean Reifschneider (jafo) *  |
Date: 2008-03-19 21:35 | |
Raymond: Can you see the other related issues and see if the proposed fix (inline in the comment) is acceptable? |
|||
| msg64403 - (view) | Author: Raymond Hettinger (rhettinger) * |
Date: 2008-03-24 08:46 | |
Unassigning. I don't have more thoughts on this one. |
|||
| msg171262 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2012-09-25 12:54 | |
Reading the original issue:
"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."
... I have a hard time believing IE is still broken today. I'd rather close this issue, please re-open if you can reproduce with a recent IE.
|
|||