Re: [quicwg/base-drafts] HTTP SETTINGS: define setting content encoding (#1556)

[Martin Thomson <[e-mail]>]

That would be a regression in my view.  There is value in having settings being able to express things other than numbers.  The fact that length is redundant is a consequence of that feature, so it doesn't bother me in the slightest.

Here's an example that might make sense, though I doubt that I would implement it... a setting that included a base URL so that request targets could be identified relative to that URL if desired.  That might be justified on the basis that we can't compress parts of header fields (for good reasons), but that particular tweak is probably safe.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1556#issuecomment-411254957