Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02)

User agents generate those headers.  They don't need instructions for
how to parse them.


On Sun, Oct 3, 2010 at 1:00 PM, Eric J. Bowman <> wrote:
> Considering this proposal elsewhere in HTTPbis:
> By your logic, since user agents (browsers) would need to continue to
> support X-Moz and X-Purpose, it would be incorrect to define the
> Purpose header and leave it at that, without also providing some
> language instructing user agents how to parse X-Moz and X-Purpose, as
> they are in fact used in the wild.
> I see describing how to parse the obsoleted headers as standardizing
> nonconformant (unspecified) syntax.  Just because it was once done this
> way, and adopted in more than one browser, isn't relevant to the
> definition of a Purpose header.  Quite relevant to browser development,
> not relevant to HTTP.
> -Eric

Received on Sunday, 3 October 2010 20:11:34 UTC