Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[assets] confirm a weak but matching ETag #3485

Closed
wants to merge 2 commits into from
Closed

[assets] confirm a weak but matching ETag #3485

wants to merge 2 commits into from

Commits on Sep 7, 2019

  1. [assets] confirm a weak but matching ETag 

    When handling compression at the proxy server level, the client receives a weak ETag.
Weak ETags are prefixed with `W/`, e.g. `W/"2.2.0"`.
Upon cache validation we should take care of these too.
    @das7pad
    das7pad committed Sep 7, 2019
    Copy the full SHA
    25e8050 View commit details
    Browse the repository at this point in the history

Commits on Sep 20, 2019

  1. [test] add an integration test for the added weak etag handling 

    REF: 25e8050
    @das7pad
    das7pad committed Sep 20, 2019
    Copy the full SHA
    bd60f44 View commit details
    Browse the repository at this point in the history