-
Is there a table for support for HTTP/2 PRIORITY_UPDATE instead of HTTP/2 PRIORITY ?
[RFC 9113 HTTP/2](https://www.rfc-editor.org/rfc/rfc9113.html#PriorityHere) [5.3.2.](https://www.rfc-editor.org/…
-
[RFC 9113 8.8.5](https://httpwg.org/specs/rfc9113.html#n-informational-responses) Gives examples of 100-continue:
```
HTTP/1.1 100 Continue HEADERS
Extension-Field: bar ==> …
-
This issue is part of a project to move x/net/http2 into std: https://github.com/golang/go/issues/67810
A HTTP/2 client or server may send PING frames to its peer. (RFC 9113 Section 6.7)
The [ht…
-
This issue is part of a project to move `x/net/http2` into `std`: #67810
This proposal depends on the version selection API proposed in #67814.
The `net/http` package does not directly support u…
neild updated
1 month ago
-
### Expected behavior
A minimal Netty HTTP/2 server should follow RFC 9113, and pass h2spec compliance (barring reasonable disagreement over any ambiguity). In particular, it should pass the 8.1.2.…
-
I was talking to @mtrudel on slack and he came up with a list of steps in order to support http/2 h2c and http2 websockets:
1. Add support for upgrade support to `bandit/http1/{adapter,handler}.ex`…
-
Thank you very much for packaging this modernised collection of djbware! I was wondering if there’s also plans underway to add support for DNS over TLS?
-
HTTP/2 uses a completely different syntax to describe requests/responses. It is not as simple as replacing `HTTP/1.1` with `HTTP/2` and adding support for pseudo-headers (which is what I see as having…
-
10ページの以下RFCですが、間違いだと思われるため、確認をお願いします。
RFC 9313 HTTP/2
-
RFC: https://www.rfc-editor.org/rfc/rfc9113#name-the-upgrade-header-field
Envoy currently allows and passes downstream 101 status from H/2 and H/3 upstreams.
Determine if 101 response needs to b…