-
## 1. 概要
## 2. 目的
## 3. 提案内容
## 4. タスク
- [ ] 細かいタスクに分解できているなら書き出す
-
https://datatracker.ietf.org/doc/html/rfc9112
What do we need to change?
New http 1.1 standard... seems to be dropping http 1.0?
-
This issue was created automatically with bugzilla2github.py
# Bugzilla Bug 480
Date: 2024-03-21T22:30:28+01:00
From: @vlcinsky
To: @ingeniumfaber
Last updated: 2024-03-21T22:30:28+01:00
-
Hi guys, I'm facing this issue where unit returns 411 content-length required when the request doesn't specify the content-length, but it actually specifies Transfer-Encoding: Chunked.
```
co…
robjr updated
3 months ago
-
It appears some rfc referenced in the 2x specification and CDMI extension documents may have been updated. We should consider an audit on impacts, if any, to the cdmi 2x specification and associated e…
-
`If-None-Match: *`: そこにあれば412 (RFC 9112 § 13.1.2)、なければ404
-
From RFC 7230:
> If a message is received with both a Transfer-Encoding and a
Content-Length header field, the Transfer-Encoding overrides the
Content-Length. Such a message might in…
-
Goals:
- [ ] Can perform HTTP requests (via a new ``HttpClient`` module) on top of the existing ``TcpClient`` implementation
- [ ] Can create HTTP servers (via a new ``HttpServer`` module) on top …
-
The function `parse_http_version` does not accept versions below HTTP/1.0. However `parse_headers` allows only LF to mark the end of header:
https://github.com/h2o/picohttpparser/blob/2a16b2365ba30b1…
-
The latest revision to HTTP/2, RFC 9112, deprecated a few things that turned out to be duds but it didn't go as far as making any breaking changes.
What if we had infinite scope to change the wire…