Bug 1773192 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0

Steps to reproduce:

Follow the hyperlink on ref1.html (attached) and click back button to return to ref1.html

ref1.html links to ref2.html

ref2.html has some javascript to cut itself out of history
history.replaceState({},"",document.referrer); 
and then loads ref3.html

Browser back button in ref3.html correctly loads ref1.html yet the http referer header is missing.


Actual results:

When clicking back button from ref3.html referer http header is not transmitted with the request to ref1.html.



Expected results:

When clicking back button from ref3.html referer http header should be transmitted with the request to ref1.html.

This worked in earlier versions of Firefox at least 72.0.2 and also works in Chrome 102.

Without the referer header web app does not display data and navigation is broken.
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0

Steps to reproduce:

Follow the hyperlink on ref1.html (attached) and click back button to return to ref1.html

ref1.html links to ref2.html

ref2.html has some javascript to cut itself out of history
`history.replaceState({},"",document.referrer); `
and then loads ref3.html

Browser back button in ref3.html correctly loads ref1.html yet the http referer header is missing.


Actual results:

When clicking back button from ref3.html referer http header is not transmitted with the request to ref1.html.



Expected results:

When clicking back button from ref3.html referer http header should be transmitted with the request to ref1.html.

This worked in earlier versions of Firefox at least 72.0.2 and also works in Chrome 102.

Without the referer header web app does not display data and navigation is broken.

Back to Bug 1773192 Comment 0