h11 icon indicating copy to clipboard operation
h11 copied to clipboard

A pure-Python, bring-your-own-I/O implementation of HTTP/1.1

Results 42 h11 issues
Sort by recently updated
recently updated
newest added

Closely related to #97. Prompted by https://github.com/encode/httpx/issues/1363#issuecomment-709706049 So, h11 currently has stricter-than-urllib3 rules on header name validation... ```python >>> import httpx >>> httpx.get("https://club.huawei.com/") Traceback (most recent call last): ... httpx.RemoteProtocolError:...

Considering for example this snippet of code ``` def run(target): conn = h11.Connection(our_role=h11.CLIENT) sock = socket.create_connection((target, 80)) request = h11.Request(method="GET", target="/", headers=[("Host", target)]) data = conn.send(request) sock.sendall(data) data = sock.recv(2048)...

Prompted by https://github.com/encode/httpx/discussions/1735 When a server uses chunked encoding, but erroneously includes whitespace between the `` and the ``, a `RemoteProtocolError` is raised... ```pycon >>> import h11 >>> state =...

This is based on #118, please look at the last commit only. (Sorry for the jungle of PRs, I can rebase them whichever way). --- It somewhat obscures the control...

On the premise of keeping Pure-Python h11, maybe `.pxd` + `Cython` can be used to improve performance? Related links: https://cython.readthedocs.io/en/stable/src/tutorial/pure.html#augmenting-pxd

According to the spec, all HTTP/1.1 requests MUST have a `Host:` header. Currently h11 enforces this. @jab pointed me to this issue that go ran into in 2017 trying to...

The server I was trying to reach return every response with this line in header which raise RemoteProtocolError. I tried to forge a response with the header line, showing it...

I have been using h11 for a while now. In my code, I made a copy of the headers like this: ```python headers = ev.headers[:] ``` That is the normal...

Not running it on CI or anything, just for developers who want to run it locally. (If we do want to add it to CI and tox I'll happily add...

Header values are a mess. Supposedly they're defined by RFC 7230, but in fact it has a bug and its definition is obviously wrong. And, in practice, implementations are substantially...