1694829 - When you go to a page that has a 404 not found, and you navigate back you still get the 404 page in the debugger

Status: RESOLVED WORKSFORME

(DevTools :: Debugger, defect)

Description

[ntrots.maling]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

i have a simple sapper app (like next.js for svelte) and i add a link to a non-existend page it gets a 404 not found status code. I then press the back button and look at the debugger.

Actual results:

The debugger shows the 404 page the server responded with.

Expected results:

It shouldn't show up as the request returns a 404 status code (i checked)

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Hubert Boma Manilla (:bomsy)]

Thanks for reporting!

Would you be able to provide a next js sample app we can use to reproduce?

Comment 3

[ntrots.maling]

Sorry for the late reply, i couldn't log in to my account

https://github.com/SamuelFischerCode/bugzillaBug
just download and run npm install && npm run dev

Comment 4

[Hubert Boma Manilla (:bomsy)]

Thank you for the sample app.

I was not able to reproduce the issue.

Here is the STR i used

1. After downloading, installing and running the app you provided above
2. Open firefox
3. Go to http://localhost:3000/
4. Open the debugger
5. Click the Jobs link which show a 404 page
6. In the Debugger sources panel on the left, i see the jobs 404 page
7. i click that, it shows the code for that page.
8. Then i press the back button

Actual results:
The source panel refreshes and the opened jobs 404 page in the debugger goes away

Does this STR match you were doing? And is this still broken for you?

Comment 5

[Julian Descottes [:jdescottes]]

No update for 2 months, also tried the STRs and can't reproduce. Closing.