[
https://issues.apache.org/jira/browse/TS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654078#comment-14654078
]
Leif Hedstrom edited comment on TS-3497 at 8/4/15 6:14 PM:
-----------------------------------------------------------
I spoke with [[email protected]] on this, and we agreed that we would much
prefer the usage of an appropriate constructor for the Http2Error(), such that
you'd write e.g.
{code}
return Http2Error(HTTP2_ERROR_CLASS_CONNECTION, HTTP2_ERROR_PROTOCOL_ERROR);
{code}
Please make that change, and we'll land this for 6.0.0.
Thanks,
-- leif
was (Author: zwoop):
I spoke with [[email protected]] on this, and we agreed that we would much
prefer the usage of a copy constructor for the Http2Error(), such that you'd
write e.g.
{code}
return Http2Error(HTTP2_ERROR_CLASS_CONNECTION, HTTP2_ERROR_PROTOCOL_ERROR);
{code}
Please make that change, and we'll land this for 6.0.0.
Thanks,
-- leif
> Malformed requests must be treated as a stream error
> ----------------------------------------------------
>
> Key: TS-3497
> URL: https://issues.apache.org/jira/browse/TS-3497
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP/2
> Reporter: Masakazu Kitajo
> Assignee: Masakazu Kitajo
> Fix For: 6.0.0
>
>
> Malformed requests must be treated as a stream error, but currently it's
> treated as a connection error.
> {quote}
> Malformed requests or responses that are detected MUST be treated as a stream
> error (Section 5.4.2) of type PROTOCOL_ERROR.
> {quote}
> https://tools.ietf.org/html/draft-ietf-httpbis-http2-17#section-8.1.2.6
> I found this behavior with these requests:
> - Uppercase header field names
> - Empty :path header
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
