fix field-value ABNF #19

Open
reschke opened this Issue Aug 10, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@reschke
Contributor

reschke commented Aug 10, 2016

@reschke reschke referenced this issue in whatwg/fetch Aug 10, 2016

Closed

Header value definition needs work #332

@annevk

This comment has been minimized.

Show comment
Hide comment
@annevk

annevk Jan 11, 2017

In the range 0x00-0x7F Chrome, Edge, and Firefox all seem to only do something special with 0x00, 0x0A, and 0x0D. Everything else goes. Chrome and Firefox also apply this to the range 0x7F-0xFF. Edge starts transmitting UTF-8 bytes for those "code points" instead... Safari Technology Preview restricts 0x00-0x1F and 0x7F.

It seems easiest to simply not have constrains here.

annevk commented Jan 11, 2017

In the range 0x00-0x7F Chrome, Edge, and Firefox all seem to only do something special with 0x00, 0x0A, and 0x0D. Everything else goes. Chrome and Firefox also apply this to the range 0x7F-0xFF. Edge starts transmitting UTF-8 bytes for those "code points" instead... Safari Technology Preview restricts 0x00-0x1F and 0x7F.

It seems easiest to simply not have constrains here.

@annevk

This comment has been minimized.

Show comment
Hide comment
@annevk

annevk Jun 20, 2018

Note that in whatwg/xhr#165 I've been trying to get browsers to align on rejecting responses where a header value contains a 0x00. Not much progress thus far, but I do still expect success eventually.

annevk commented Jun 20, 2018

Note that in whatwg/xhr#165 I've been trying to get browsers to align on rejecting responses where a header value contains a 0x00. Not much progress thus far, but I do still expect success eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment