I've had this problem too

Tried testing the issue on reported chrome version #70.0.3538.110 using Windows 10 by following below steps.

Steps:
=====
1.Launched chrome.
2.Opened "index.html".
3.Clicked on the link "To page2".
4.Observed that it navigated to "page3.html".
5.When clicked chrome back button it landed on "index.html"

Attached screencast for reference.
@reporter: Could you please review attached screencast and let us know if anything is missed here. Retry the issue on latest stable chrome #71.0.3578.98 without any apps and extensions in it, reset all flags to default and let us know if the issue still persists. You can download the latest chrome from- "https://www.chromium.org/getting-involved/dev-channel".
Thanks.!

Deleted: 916543.mp4 632 KB

	916543.mp4 632 KB View Download

I believe this is intentional, to prevent developers from breaking the back button and not letting users leave the website.

Your screencast sums up the error very well.

When you click the back button in Chrome, you land on index.html which is not the intended behaviour. You should land on page2.html which again redirects you to to page3.html.

I understand that this might be intentional to keep developers from breaking the back button. But in my use case you the user lands on a page which only purpose is to to send an asynch request to an API and thereafter redirect the user to a receipt page.
If the user then clicks the back button we want to make sure the request is not sent again and instead supply the user with an informational message saying something like: "you have already completed this action, please go to your dashboard".
Instead, what happens is that the user, when clicking the back button, is transported to the page before the one where the request is sent and that is not what we want.

I could throw a timeout on the page, in that case it is added to the history but I am reluctant to do that because:
A: this is only an issue in Chrome.
B: It causes unnecessary delays.
C: It is not good practice.
D: I do not know how long that timeout should be, what is the magic number of (milli)seconds to wait before redirecting the user?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue on chrome reported version# 70.0.3538.110  #71.0.3578.98 and on latest chrome# 73.0.3664.0 with test files provided in comment# 0 using Mac 10.12.6, Windows-10 and Ubuntu 17.10. As this issue is seen from M-60(60.0.3112.0), hence considering this as Non-Regression and marking it as Untriaged.

Thanks!