-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
What should happen with location.reload() on a page that is a POST result? #3215
Comments
I wonder how @mcmanus feels about removing the prompting. As I understand it servers already need to be resilient against duplicate POSTs due to various protocol issues. Given that, it seems unfortunate to have a dialog the user isn't really helped with (or can typically make sense of). |
The prompting is a separate issue. This issue is about the server-observable behavior: does the POST get resent at all? |
Understood and we should fix that, but I'm wondering if the new language (and tests) needs to account for the prompting or not. |
Consider this testcase:
I can't do step 3 in Safari, because it won't let me open developer tools on that page. But in Chrome, Firefox, and Edge, in step 3 the reload resends the POST data. Firefox and Edge prompt for the repost; Chrome just silently does it.
If I read the spec right, we're in https://html.spec.whatwg.org/multipage/history.html#dom-location-reload in the "Otherwise" case, which just says to navigate to the document's URL, ignoring any POST data, which doesn't match the above-described browser behavior.
The text was updated successfully, but these errors were encountered: