[jira] [Comment Edited] (TS-2812) header_normalize to convert lower case spdy hdrs to camel case for backward compatibility
[ https://issues.apache.org/jira/browse/TS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009819#comment-14009819 ] Sudheer Vinukonda edited comment on TS-2812 at 5/27/14 3:48 PM: Leif - this is a temporary workaround for interworking with legacy/old origins that can't support lower case SPDY headers. I wrote it for our use, but, posted a jira patch on [~bcall]'s recommendation. I will leave it up to you to decide whether or not it is needed in 5.0. Thanks! was (Author: sudheerv): Leif - this is a temporary workaround for interworking with legacy/old origins that can't support lower case SPDY headers. I wrote it for our use, but, posted a jira patch on ~[bcall]'s recommendation. I will leave it up to you to decide whether or not it is needed in 5.0. Thanks! 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)
[jira] [Comment Edited] (TS-2812) header_normalize to convert lower case spdy hdrs to camel case for backward compatibility
[ https://issues.apache.org/jira/browse/TS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009834#comment-14009834 ] James Peach edited comment on TS-2812 at 5/27/14 4:00 PM: -- As per my previous comment, we should fix the root cause and not paper over the problems with additional plugins. I'll be happy to take a patch to fix the TSFetch API; or a patch to SPDY to not use it. was (Author: jamespeach): As per my previous comment, we should fix the root cause and not paper over the problems with additional plugins. 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)
[jira] [Comment Edited] (TS-2812) header_normalize to convert lower case spdy hdrs to camel case for backward compatibility
[ https://issues.apache.org/jira/browse/TS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000990#comment-14000990 ] Sudheer Vinukonda edited comment on TS-2812 at 5/18/14 4:14 AM: 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 are being enhanced 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. was (Author: sudheerv): 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)
[jira] [Comment Edited] (TS-2812) header_normalize to convert lower case spdy hdrs to camel case for backward compatibility
[ https://issues.apache.org/jira/browse/TS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000990#comment-14000990 ] Sudheer Vinukonda edited comment on TS-2812 at 5/18/14 4:15 AM: 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 are being enhanced to accept headers in any case. On the other hand, if we change the implementation to ALWAYS send camel case headers, that would be eventually 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. was (Author: sudheerv): 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 are being enhanced 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)
