[ 
https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652739#comment-14652739
 ] 

Leif Hedstrom commented on TS-3814:
-----------------------------------

Are you sure you can't just do e.g.

{code}
diff --git a/proxy/http2/HTTP2.cc b/proxy/http2/HTTP2.cc
index 26c7d57..75da32e 100644
--- a/proxy/http2/HTTP2.cc
+++ b/proxy/http2/HTTP2.cc
@@ -701,7 +701,7 @@ http2_parse_header_fragment(HTTPHdr *hdr, IOVec iov, 
Http2DynamicTable &dynamic_
     }

     // rfc7540,sec8.1.2.2: Any message containing connection-specific header 
fields MUST be treated as malformed
-    if (ptr_len_casecmp(name, name_len, MIME_FIELD_CONNECTION, 
MIME_LEN_CONNECTION) == 0) {
+    if (name ==  MIME_FIELD_CONNECTION) {
       return HPACK_ERROR_HTTP2_PROTOCOL_ERROR;
     }
{code}


> Treat requests with Connection header field as malformed
> --------------------------------------------------------
>
>                 Key: TS-3814
>                 URL: https://issues.apache.org/jira/browse/TS-3814
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP/2
>            Reporter: Ryo Okubo
>             Fix For: 6.0.0
>
>         Attachments: sec8_1_2_2.patch
>
>
> According to [Section 8.1.2.2 in 
> RFC7540|https://tools.ietf.org/html/rfc7540#section-8.1.2.2], H2 requests 
> with Connection header field should be treated as malformed. But current ATS 
> passes them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to