Repository navigation
What should happen with location.reload() on a page that is a POST result? #3215
Description
Consider this testcase:
<form action="/?url=https%3A%2F%2Fsoftware.hixie.ch%2Futilities%2Fcgi%2Ftest-tools%2Fecho" method=post>
<input type="submit" name="something" value="Submit me">
</form>
- Load the testcase.
- Click the button.
- Open developer tools and evaluate "location.reload()".
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.
Activity
bzbarsky commentedon Nov 8, 2017
// cc @annevk @domenic
annevk commentedon Nov 9, 2017
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).
bzbarsky commentedon Nov 9, 2017
The prompting is a separate issue. This issue is about the server-observable behavior: does the POST get resent at all?
annevk commentedon Nov 9, 2017
Understood and we should fix that, but I'm wondering if the new language (and tests) needs to account for the prompting or not.