Closed kenballus closed 1 year ago
@kenballus the spec is not very clear, but I think I agree with you is that the intention is that there's no quotes here. My guess is that the quotes are allowed in places where the grammar says token
, and in this case they explicitly say a bunch of digits.
It's not hugely important, but could you edit the PR to remove the parens around the PositiveNum64
, as this would be the idiomatic way to write it, so: SepBy1 PositiveNum { ... }
When I try to feed the generated examples to my parsers, they complain because the Content-Length values are quoted.
HTTP.ddl
says this:The relevant portion of the RFC says this:
As far as I can tell, this isn't a universal statement about all
field-value
s; it's just saying that some headers, includingContent-Type
, can have either quoted or unquoted values. My understanding is thatContent-Length
can't have a quoted value, so this PR removes a couple ofMaybeQuoted
s.