Subject: [httpwg/http-extensions] Header fields that are valid SH, but invalid according to the definition of that field (#623)

From: HTTP issue updates <[email-masked]>
Date: Sun, 13 May 2018 23:20:47 -0700

If a header field is valid according to SH, but invalid according to some additional constraints that are included in the definition of the specific header field, what happens?

* it needs to be dropped because malformed header fields are dropped according to SH

* the definition of the specific header field needs to define what happens in this case

-- 
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/623