[secdir] WWW-Authenticate parsing quirks, was: SECDIR review of draft-ietf-httpbis-p7-auth-24

[Julian Reschke <[e-mail]>]

On 2013-10-29 20:35, Stephen Kent wrote:
> ...
> In Section 4.4 the text says:
>
> Note: The challenge grammar production uses the list syntax as
>
> well.Therefore, a sequence of comma, whitespace, and comma can
>
> be considered both as applying to the preceding challenge, or to
>
> be an empty entry in the list of challenges.In practice, this
>
> ambiguity does not affect the semantics of the header field value
>
> Should “both” be “either” in the above text? Does the potentially
 > ...

Yes (done)

> ambiguous construct ever take on both meanings simultaneously?
> ...

Yes, but these two meanings do not affect the semantics of the header 
field as a whole (it's either an empty entry in the list of auth 
parameters, or an empty challenge value).

Best regards, Julian