- From: Martin Thomson <mt@lowentropy.net>
- Date: Mon, 25 Sep 2023 12:30:08 +1000
- To: "Lucas Pardue" <lucaspardue.24.7@gmail.com>
- Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
On Mon, Sep 25, 2023, at 11:25, Lucas Pardue wrote: > For the content-length matter I mentioned above, my implementation > generates a 4xx in H2 and H3. I don't plan to change that. Content-Length has always been a bit of an awkward fit in the specification. Maybe you are right to say that you want to signal that error at the HTTP layer, but would you say the same if you received a SETTINGS frame on a request stream or one of the many other errors specified in the RFC? It would be best if these sorts of divergences from what we specified were documented in the specification, don't you think?
Received on Monday, 25 September 2023 02:30:33 UTC