[issue28548] http.server parse_request() bug and error reporting

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +986 ___ Python tracker ___ ___

[issue28548] http.server parse_request() bug and error reporting

2016-11-18 Thread Martin Panter
Martin Panter added the comment: Okay committed to 3.7 for the moment. I think that is all we can reasonably do unless we drop the pseudo-HTTP-0.9 support. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python

[issue28548] http.server parse_request() bug and error reporting

2016-11-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7c98768368cb by Martin Panter in branch 'default': Issue #28548: Parse HTTP request version even if too many words received https://hg.python.org/cpython/rev/7c98768368cb -- nosy: +python-dev ___ Python

[issue28548] http.server parse_request() bug and error reporting

2016-10-31 Thread Martin Panter
Changes by Martin Panter : -- versions: +Python 3.7 -Python 3.5 Added file: http://bugs.python.org/file45300/parse-version.v2.patch ___ Python tracker

[issue28548] http.server parse_request() bug and error reporting

2016-10-29 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Oct 29, 2016, at 02:20 AM, Martin Panter wrote: >Here is a patch to parse the version from the request in more cases. Since it >is more of a cosmetic improvement for handling erroneous requests, I would >probably only apply it to the next Python version

[issue28548] http.server parse_request() bug and error reporting

2016-10-28 Thread Martin Panter
Martin Panter added the comment: Here is a patch to parse the version from the request in more cases. Since it is more of a cosmetic improvement for handling erroneous requests, I would probably only apply it to the next Python version (3.7 atm). Or do you think it should go into bug fix

[issue28548] http.server parse_request() bug and error reporting

2016-10-28 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Oct 28, 2016, at 10:57 PM, Martin Panter wrote: >Parsing the version from words[-1] rather than words[2] may be a minor >improvement however. Indeed; I thought about that too. -- ___ Python tracker

[issue28548] http.server parse_request() bug and error reporting

2016-10-28 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Oct 28, 2016, at 10:42 PM, Martin Panter wrote: >I think you should be able to reproduce this without Mailman or tox, by just >running “python -m http.server”. Yep, indeed. >The problem is the “HTTP/0.9” protocol that Python is assuming does not >include

[issue28548] http.server parse_request() bug and error reporting

2016-10-28 Thread Martin Panter
Martin Panter added the comment: Parsing the version from words[-1] rather than words[2] may be a minor improvement however. -- ___ Python tracker ___

[issue28548] http.server parse_request() bug and error reporting

2016-10-28 Thread Martin Panter
Martin Panter added the comment: I think you should be able to reproduce this without Mailman or tox, by just running “python -m http.server”. The problem is the “HTTP/0.9” protocol that Python is assuming does not include a header section, so there is no place to put a 400 status code or

[issue28548] http.server parse_request() bug and error reporting

2016-10-28 Thread Barry A. Warsaw
New submission from Barry A. Warsaw: This might also affect other Python version; I haven't checked, but I know it affects Python 3.5. In Mailman 3, we have a subclass of WSGIRequestHandler for our REST API, and we got a bug report about an error condition returning a 400 in the body of the