[
https://issues.apache.org/jira/browse/TS-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masaori Koshiba updated TS-4209:
--------------------------------
Description:
TS is using concurrent stream limit which is advertised *from* clients now.
TS MUST use concurrent stream limit which is configured by
{{proxy.config.http2.max_concurrent_streams_in}} and advertised *to* clients.
RFC 7540 says below in
[5.1.2|http://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2]
{quote}
An endpoint that receives a HEADERS frame that causes its advertised concurrent
stream limit to be exceeded MUST treat this as a stream error (Section 5.4.2)
of type PROTOCOL_ERROR or REFUSED_STREAM.
{quote}
was:
TS using concurrent stream limit which is advertised *from* clients now.
TS MUST use concurrent stream limit which is configured by
{{proxy.config.http2.max_concurrent_streams_in}} and advertised *to* clients.
RFC 7540 says below in
[5.1.2|http://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2]
{quote}
An endpoint that receives a HEADERS frame that causes its advertised concurrent
stream limit to be exceeded MUST treat this as a stream error (Section 5.4.2)
of type PROTOCOL_ERROR or REFUSED_STREAM.
{quote}
> Limit concurrent streams correctly
> ----------------------------------
>
> Key: TS-4209
> URL: https://issues.apache.org/jira/browse/TS-4209
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
> Reporter: Masaori Koshiba
> Assignee: Masaori Koshiba
> Fix For: 6.2.0
>
>
> TS is using concurrent stream limit which is advertised *from* clients now.
> TS MUST use concurrent stream limit which is configured by
> {{proxy.config.http2.max_concurrent_streams_in}} and advertised *to* clients.
> RFC 7540 says below in
> [5.1.2|http://httpwg.org/specs/rfc7540.html#rfc.section.5.1.2]
> {quote}
> An endpoint that receives a HEADERS frame that causes its advertised
> concurrent stream limit to be exceeded MUST treat this as a stream error
> (Section 5.4.2) of type PROTOCOL_ERROR or REFUSED_STREAM.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)