You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
carllerche opened this issue
Nov 14, 2017
· 4 comments
Labels
A-headersArea: HTTP headersB-rfcBlocked: request for comments. More discussion would help move this along.S-featureSeverity: feature. This adds something new.
I had this exact thought while writing that PR, but also this conflicting thought: both are non-standard headers that we (HTTP in general) want to go away.
Could we add them but make them doc hidden or something?
I don't think we could use const fn here, since we have to validate the bytes. A procedural macro could eventually exist to compile-time check/create header names...
A-headersArea: HTTP headersB-rfcBlocked: request for comments. More discussion would help move this along.S-featureSeverity: feature. This adds something new.
The HTTP/2.0 spec requires implementations to verify that these headers do not get included in outbound messages, and thus must check for them.
Providing constants would help speed up these checks.
The text was updated successfully, but these errors were encountered: