New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reprioritize blocking asset files (`.js`, `.css`) for Chrome #349

merged 4 commits into from Jun 2, 2015


None yet
1 participant

kazuho commented Jun 2, 2015

At the moment, Chrome falls behind Firefox in prioritizing the asset files, as discussed in

This PR implements a workaround in the server-side by raising the priority to maximum of requests that are likely against asset files. The reprioritization is not applied to HTTP2 connections that use priority trees (e.g. Firefox).

kazuho added some commits Jun 2, 2015

sheduler_set_weight should allow weight=257 (which is used internally…
… for push etc.)

note: no need to check if weight is above 256 for network input, since it comes in as a single-byte value (bet. 1 and 256)

kazuho added a commit that referenced this pull request Jun 2, 2015

Merge pull request #349 from h2o/kazuho/reprioritize-blocking-assets
reprioritize blocking asset files (`.js`, `.css`) for Chrome

@kazuho kazuho merged commit 7048056 into master Jun 2, 2015

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
continuous-integration/travis-ci/push The Travis CI build passed

@kazuho kazuho referenced this pull request Aug 12, 2015


cache-aware server-push #421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment