[
https://issues.apache.org/jira/browse/TS-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234444#comment-15234444
]
ASF subversion and git services commented on TS-4087:
-----------------------------------------------------
Commit e7951c69d4b2efd82faebbb565d162987f67a7a8 in trafficserver's branch
refs/heads/master from [~masaori]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e7951c6 ]
TS-4087: Docs: About new settings to limit streams
> H2 flexible resource limitation
> -------------------------------
>
> Key: TS-4087
> URL: https://issues.apache.org/jira/browse/TS-4087
> Project: Traffic Server
> Issue Type: New Feature
> Components: HTTP/2
> Reporter: Ryo Okubo
> Assignee: Masaori Koshiba
> Fix For: 6.2.0
>
>
> Current H2 implementation depends on FetchSM and PluginVC to forward
> requests. But their memory footprint is very high. It may be vulnerable to
> DoS attack.
> As simple ways to avoid the problem, we can use two limitations,
> _proxy.config.net.connections_throttle_ and
> _proxy.config.http2.max_concurrent_streams_in_. But reducing number of
> _proxy.config.net.connections_throttle_ causes that number of acceptable
> HTTP/1.1 requests become lower. And reducing
> _proxy.config.http2.max_concurrent_streams_in_ restricts benefits of H2.
> I'd like to propose more flexible resource limitation for current H2 impl
> based on number of active H2 streams. Its adding an upper limit of active H2
> streams. If tis exceeded, ATS send low number of
> SETTINGS_MAX_CONCURRENT_STREAMS to clients and/or RST_STREAM frame.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
