Github user maskit commented on the issue:
https://github.com/apache/trafficserver/pull/830
Talked with Masaori offline.
- Chrome seems creating a deep depth tree intentionally to get contents in
the order that Chrome wants
- Using SETTINGS_MAX_CONCURRENT_STREAMS as the limit is reasonable because
the tree depth doesn't over the setting value even if the tree nodes are
created in the Chrome way
- There would be no serious issue even if all clients were Chrome
So, +1 from me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
