Github user masaori335 commented on the issue:
https://github.com/apache/trafficserver/pull/830
Yes, we don't have to follow it, but we should follow it as much as
possible. Because it could be happen that images are sent before CSS/JS, if we
don't follow it.
How about use SETTINGS_MAX_CONCURRENT_STREAMS as the max depth? It looks
appropriate and we don't need new configures.
I'm seeing that with latest Chrome ( 51.0.2704.106 ). Chrome had that bug
in Feb and reverted the changes. IIUC, the bug is about the order of streams
not depth of streams. Now (maybe from Jun), it looks like they fixed the order
and rolled it out.
---
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.
---
