This issue occurs as explained by the reporter: After running the node.js app provided by the reporter and trying the steps provided by him in any of the 3 main Mozilla version (nightly - v62.0a1, beta - 60.0, release - 59.0.3), the issue is reproduced (after clicking the browser's back button on page 2, the user is not redirected to page 1, but back to page 2). This issue does not occur on the Chrome browser.
Status: UNCONFIRMED → NEW
status-firefox60: --- → affected
status-firefox62: --- → affected
Component: Untriaged → Document Navigation
Ever confirmed: true
Product: Firefox → Core
I don't find anything in the spec that says to omit a history entry if a script navigates away from the page before the load completes. Is there such spec language? Should there be?
Priority: -- → P4
I don't think so and maybe; in large part this is also governed by UI choices that are very much up to the user agent. However, if this is a prevalent pattern as indicated by OP it should probably be covered.
(In reply to Henri Sivonen (:hsivonen) from comment #2) > I don't find anything in the spec that says to omit a history entry if a > script navigates away from the page before the load completes. Is there such > spec language? Should there be? After some additional experimentation, it seems that the issue is not whether to omit the URL of the current page from the history, but whether to replace it with the target URL of POST request. Please see the blog post https://pomcor.com/2018/05/16/a-bypass-of-the-firefox-post-redirection-bug/
You need to log in before you can comment on or make changes to this bug.