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

ABNF for "parameter" #65

Closed
reschke opened this issue Apr 23, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@reschke
Copy link
Contributor

commented Apr 23, 2015

Bence Béky in http://lists.w3.org/Archives/Public/ietf-http-wg/2015AprJun/0220.html:

"I need some clarification. I am writing a parser for ALTSVC header
fields and wish to ignore unknown parameters. However, it is unclear
to me whether a parameter without "=value" should be ignored or
treated as malformed.

draft-ietf-httpbis-alt-svc-06 Section 3 refers to "parameter".
Section 1.1 says "parameter" is defined in RFC7230. In fact, RFC7230
has "transfer-parameter" but not "parameter". Also, RFC7230 Section
says "Parameters are in the form of a name or name=value pair.",
implicilty allowing names without values, but in the next line
"transfer-parameter" is defined as a name=value pair, which disallowes
names without values. On the other hand, RFC7231 Section 3.1.1.1
defines "parameter" as a name=value pair, but this is not what
draft-ietf-httpbis-alt-svc-06 refers to."

reschke added a commit that referenced this issue Apr 30, 2015

@reschke reschke closed this Apr 30, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.