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.

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

History traversal fetches should be "force-cache", or "only-if-cached" #6601

Open
jakearchibald opened this issue Apr 21, 2021 · 0 comments
Open
Assignees

Comments

@jakearchibald
Copy link
Contributor

jakearchibald commented Apr 21, 2021

From poking browsers, it seems like, when you traverse to a history entry without a document, that document is fetched using cache mode:

In Firefox/Chrome:

  • "force-cache" if the request is GET.
  • "only-if-cached" if the request is POST.

In Safari:

  • "force-cache" if the request is GET.
  • "default" (maybe?) if the request is POST.

Some of this split is because Safari shows a prompt to resubmit form data on traversal, whereas Firefox/Chrome show an error on traversal. I prefer the Firefox/Chrome behaviour for the reasons in #6600

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

No branches or pull requests

2 participants