You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Masakazu Kitajo (JIRA)" <ji...@apache.org> on 2015/04/10 17:49:12 UTC

[jira] [Comment Edited] (TS-3497) Malformed requests must be treated as a stream error

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

Masakazu Kitajo edited comment on TS-3497 at 4/10/15 3:48 PM:
--------------------------------------------------------------

Actually, treating a stream error as a connection error is allowed.

{quote}
An endpoint can end a connection at any time.  In particular, an endpoint MAY choose to treat a stream error as a connection error. Endpoints SHOULD send a GOAWAY frame when ending a connection, providing that circumstances permit it.
{quote}
https://tools.ietf.org/html/draft-ietf-httpbis-http2-17#section-5.4.1

However, such a behavior would spoil all other streams on the connection. We ought to avoid it to keep the damage at a minimum.


was (Author: maskit):
Actually, treating a stream as a connection error is allowed.

{quote}
An endpoint can end a connection at any time.  In particular, an endpoint MAY choose to treat a stream error as a connection error. Endpoints SHOULD send a GOAWAY frame when ending a connection, providing that circumstances permit it.
{quote}
https://tools.ietf.org/html/draft-ietf-httpbis-http2-17#section-5.4.1

However, such a behavior would spoil all other streams on the connection. We ought to avoid it to keep the damage at a minimum.

> 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)