[
https://issues.apache.org/jira/browse/TS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000990#comment-14000990
]
Sudheer Vinukonda commented on TS-2812:
---------------------------------------
James - thanks for the input; So, are you suggesting to ALWAYS use camel case
headers?
The main idea behind writing this plugin is that, this should only be
required/used on a need basis and only in the interim, while the legacy systems
enhance to accept headers in any case. On the other hand, if we change the
implementation to ALWAYS send camel case headers, that would be incompatible
with HTTP2 (HTTP/2 mandates the sender to use lowercase headers (and the
receiver to do a case-insensitive comparison) as well as inefficient, when not
required, right?
http://tools.ietf.org/html/draft-ietf-httpbis-http2-12#section-8.1.3
"Just as in HTTP/1.x, header field names are strings of ASCII
characters that are compared in a case-insensitive fashion. However,
header field names MUST be converted to lowercase prior to their
encoding in HTTP/2."
> header_normalize to convert lower case spdy hdrs to camel case for backward
> compatibility
> -----------------------------------------------------------------------------------------
>
> Key: TS-2812
> URL: https://issues.apache.org/jira/browse/TS-2812
> Project: Traffic Server
> Issue Type: New Feature
> Components: SPDY
> Reporter: Sudheer Vinukonda
> Labels: spdy, yahoo
> Attachments: ts2812.diff
>
>
> During our SPDY testing, we observed that certain legacy systems are not able
> to handle lower case hdrs mandated by SPDY (and even http 1.0). This simple
> plugin converts the lowercase header names into camel case and could be used
> as an interim solution until the legacy systems are upgraded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
