Subject: [httpwg/http-extensions] structured-headers: Why ignore UTF-8? (#537)

From: HTTP issue updates <[email-masked]>
Date: Tue, 27 Mar 2018 22:11:40 -0700

I noticed the structured headers proposal strictly ignores UTF-8, because it's not used much. The recommendation is to use the binary format instead.

I thought that [RFC8187](https://tools.ietf.org/html/rfc8187) was fairly good for this.

I can see structured-headers to be a super useful generic way to describe new standard and proprietary headers, but ignoring UTF-8 means we're limited in what categories of data probably unsafe for the purpose of a header.

Is there a possibility to merge the syntax of RFC8187? It's true that it might not be used as much in practice, but it might expand the potential use-cases. Furthermore, as an implementor I don't have to worry about what someone might encode. The binary format doesn't quite cut it, because it provides to hint as to how a generic client might decode it.  

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/537