Re: TE / transfer-coding issue with qvalue and transfer-parameters — HTTP/1.1, HTTP/2.0

On 2014-02-03 12:41, Simon Yarde wrote:
> Thanks Julian — I noticed this in my docs and felt it would be worth throwing out there in view of the push to wrap-up soon.
>
>> For TE and Accept-Encoding the simplest possible fix is to add that to the sections about considerations for new encodings. Note that registration of both transfer codings and content codings require "IETF Review", so that bar is relatively high anyway.
>
> This seems eminently sensible and unlikely to disrupt the review findings, since it simply replicates an accepted approach to add clarity.
>
> That said, it still isn't possible to directly implement parsers for media-type and transfer-coding ABNF rules, and by association the TE and Accept rules.
> ...

Why exactly is the ABNF a problem?

Best regards, Julian

Received on Monday, 3 February 2014 12:12:26 UTC