[go: nahoru, domu]
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

Recommend that a browser "reload" contacts the logical origin #295

Open
ithinkihaveacat opened this issue Aug 23, 2018 · 1 comment
Open

Recommend that a browser "reload" contacts the logical origin #295

ithinkihaveacat opened this issue Aug 23, 2018 · 1 comment

Comments

@ithinkihaveacat
Copy link
Contributor
ithinkihaveacat commented Aug 23, 2018 •
edited
Loading

Recommend that if the user hits the "reload" button in their browser, the browser will contact the logical origin (i.e. the URL that is visible in the browser's URL bar) to determine freshness.

(Currently not specified, but seem to be the expected behaviour, see e.g. 1, 2, 3.)
@lidel
Copy link
lidel commented Nov 5, 2018 •
edited
Loading

I feel a better design would be an ability to opt out from a forced freshness check for specified time.
Think how it is possible to cache HSTS settings in the browser by including a max-age option:

  • "pressing F5 in web browser does not contact the logical origin until snapshot from SXG is max-age old"
    • max-age=0 would mean that pressing "reload" button will always contact the logical origin
    • Shift+F5 would ignore SXG just like it ignores the cache

The max-age approach is more flexible and accounts for use cases where people want to avoid sending HTTP traffic to logical origin by any means necessary (cc ipfs/in-web-browsers#121 @jimpick )

@ithinkihaveacat ithinkihaveacat mentioned this issue Jan 22, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ithinkihaveacat @lidel