Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

Developer Tools Shows Wrong Source

  • 2 respostas
  • 3 have this problem
  • 8 views
  • Last reply by tbernard

tbernard
tbernard
more options

--EDIT-- OK, did some more testing. Looks like my premise was all wrong. It turns out when developer tools goes to load the source in debugger it actually fetches the page again(?). The page in question is a sensitive page so the server redirects back to the previous step on subsequent requests.

I tried checking/unchecking the "Show Original Sources" setting hoping it would prevent the reload and just use what was originally served. Neither worked.

New question - how do I work on the originally served source when I open the debugger tab?

FYI - Firebug seems to be doing what I'm looking for - when I open it's script tab I get the source of the page I'm looking at, not the redirected result.

--ORIGINAL QUESTION-- I'm debugging a site using the built-in developer tools. The Debugger tab is showing the source for the wrong page. It seems to be cached somewhere deep down in the program. How do I correct this?

What I've tried: 

- Closed developer tools
- Closed Browser
- Ran CCleaner to clean browser cache et al
- Reopened browser
- Navigated to suspect page and opened developer tools (It pretended like it was reloading source)
- Source still wrong!?!

Is there a way to flush the cache that the developer tools uses?

To show what I'm talking about I've attached screenshots of a few lines of the developer tools debug tab and the the output of 'view source' for the exact same page.

--EDIT-- OK, did some more testing. Looks like my premise was all wrong. It turns out when developer tools goes to load the source in debugger it actually fetches the page again(?). The page in question is a sensitive page so the server redirects back to the previous step on subsequent requests. I tried checking/unchecking the "Show Original Sources" setting hoping it would prevent the reload and just use what was originally served. Neither worked. New question - how do I work on the originally served source when I open the debugger tab? FYI - Firebug seems to be doing what I'm looking for - when I open it's script tab I get the source of the page I'm looking at, not the redirected result. --ORIGINAL QUESTION-- I'm debugging a site using the built-in developer tools. The Debugger tab is showing the source for the wrong page. It seems to be cached somewhere deep down in the program. How do I correct this? What I've tried: - Closed developer tools - Closed Browser - Ran CCleaner to clean browser cache et al - Reopened browser - Navigated to suspect page and opened developer tools (It pretended like it was reloading source) - Source still wrong!?! Is there a way to flush the cache that the developer tools uses? To show what I'm talking about I've attached screenshots of a few lines of the developer tools debug tab and the the output of 'view source' for the exact same page.
Capturas de pantalla anexas

tbernard modificouno o

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History > Show All History" or "View > Sidebar > History") or via the about:permissions page.

Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks, cookies, passwords, cache, history, and exceptions, so be cautious. If you have a password or other data from that domain that you do not want to lose then make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of the involved files.

If you revisit a 'forgotten' website then data from that website will be saved once again.

tbernard
tbernard Question owner
more options

Thanks cor-el. That's a useful feature I never knew about.

Unfortunately it didn't solve the problem. As I did more testing I realized my original assumptions may have been wrong. The question has been edited accordingly.