http-core
http-core copied to clipboard
httpwg
Core HTTP Specifications
While reviewing https://github.com/web-platform-tests/wpt/pull/34384 I noticed that the `Range` request header has a rather unusual production, in that it allows for commas, but what can come before and after the comma...
: > The 301 (Moved Permanently) status code indicates that the [target resource](https://httpwg.org/specs/rfc9110.html#target.resource) has been assigned a new permanent URI and any future references to this resource ought to use...
has: > A user agent SHOULD send Content-Length in a request when the method defines a meaning for enclosed content and it is not sending [Transfer-Encoding](https://httpwg.org/specs/rfc9112.html#field.transfer-encoding). For example, a user...
See .
1. RFC 9110 says that messages containing invalid Content-Length header field values MUST NOT be forwarded with the invalid header intact: > Likewise, a sender MUST NOT forward a message...
Can you clarify what RFC9110 requires a caching intermediary to do (or not do) with a GET request with "If-Match"? RFC9110 [13.1.1 If-Match](https://httpwg.org/specs/rfc9110.html#field.if-match) says that "A cache or intermediary MAY...
See https://www.rfc-editor.org/errata/eid7744
Hello all! I'm making my way through RFC 9111 and am finding a few bits to be potentially contradictory. In some cases, I think I understand the intention and the...
Imagine there's an origin with a chain of caches in front of it, and the caches' clocks are known to be well-synchronized with the origin's clock — perhaps because the...
I would like to discuss how we may improve the clarity of the specification with respect to informational responses. Thanks in advance for everyone's efforts in discussing this matter. Firstly,...
