sicarius noidea added the comment:
Alright, that was a bad idea.
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
sicarius noidea added the comment:
Hi @christian.heimes,
Thank you for your research too. We've also discovered that this check is
correct, but this check is very strict and blocking (error raised, stopping the
connection), we should maybe be more "laxist" and allow the lo
sicarius noidea added the comment:
Here is the poc for this error with http.client only (for the server: use the
same nc command as my first message): ```python
import http.client
>>> h1 = http.client.HTTPConnection("127.0.0.1:80")
>>> h1.request("G
sicarius noidea added the comment:
Hi,
Here I'm using requests to show the behavior because it relies on python's http
lib, and it is faster/simplier to use. The Exception "BadStatusLine" is a part
or the http/client.py library.
As per the RFC2616 section 6.1 https:/
New submission from sicarius noidea :
Hey,
BadStatusLine triggered when protocol version is in lowercase.
I've encountered a server that answers "Http/1.0 404 Not Found\r\n" instead of
"HTTP/1.0 404 Not Found\r\n"
## Expected Result
Requests understanding th
