Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC 9110, section 8.6: Incorrect use of the word "exception." #1114

Open
kenballus opened this issue Feb 16, 2024 · 0 comments
Open

RFC 9110, section 8.6: Incorrect use of the word "exception." #1114

kenballus opened this issue Feb 16, 2024 · 0 comments

Comments

@kenballus
Copy link

kenballus commented Feb 16, 2024

  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 with a Content-Length header field value that does not match the ABNF above, ...

  1. It also says that there's an exception to this rule:

... with one exception: a recipient of a Content-Length header field value consisting of the same decimal value repeated as a comma-separated list (e.g, "Content-Length: 42, 42") MAY either reject the message as invalid or replace that invalid field value with a single instance of the decimal value, since this likely indicates that a duplicate was generated or combined by an upstream message processor.

An exception to a rule is a situation in which the rule does not apply. Because the above text (2) does not allow for invalid Content-Length headers to be forwarded, it therefore seems to me that it is not an exception to the rule (1).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant