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

ASF subversion and git services commented on TS-3814:
-----------------------------------------------------

Commit 1c2ea99cff9de7044226fee9c9f02b4273abae53 in trafficserver's branch 
refs/heads/6.0.x from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1c2ea99 ]

Merge branch 'master' into 6.0.x

* master:
  TS-3822 clang-analyzer: Value stored to 'stream' during its initialization is 
never read
  TS-3824 Fix #include of pcre for a couple of plugins
  TS-3825 epic plugin does not compile on OmniOS
  TS-3824 Fix #include of pcre for a couple of plugins
  TS-3658 ASAN triggers when using the escalate.so plugin
  TS-3823 Fix tests for -lpthread since the previous commit breaks on FreeBSD
  TS-3823 Fix tests for -lpthread, and undo some of TS-3308. This retains the 
support for ASAN in a cleaner way
  TS-3823 ASAN makes us forget to add -ldl on the LIBS
  TS-3811 HTTP/2 window size must not exceed 2^31-1
  TS-3497: Define Http2Error to classify errors
  TS-3799: Fix handling of padding in DATA frames
  TS-3814 Treat requests with Connection header field as malformed, as per specs
  TS-3782: Add normal scenario tests for HTTP/2


> 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: fixed_sec8_1_2_2.patch, 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