Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Can the Network Monitor preserve its log upon navigation?

  • 2 Antworten
  • 11 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von kevinoid

more options

Does the Network Monitoring component of the Firefox Developer Tools have a way to preserve its log upon navigation (which would otherwise be cleared), similar to the Chrome or Safari Developer Tools "Preserve log upon navigation" button?

I've tried checking the "Enable persistent logs" option for the Web Console in settings, but it does not appear to affect the Network Monitoring tab. I also didn't see any bugs filed for it, so I just wanted to make sure I wasn't overlooking something obvious.

Thanks, Kevin

Does the Network Monitoring component of the Firefox Developer Tools have a way to preserve its log upon navigation (which would otherwise be cleared), similar to the Chrome or Safari Developer Tools "Preserve log upon navigation" button? I've tried checking the "Enable persistent logs" option for the Web Console in settings, but it does not appear to affect the Network Monitoring tab. I also didn't see any bugs filed for it, so I just wanted to make sure I wasn't overlooking something obvious. Thanks, Kevin

Geändert am von kevinoid

Ausgewählte Lösung

Hi kevinoid,

Thank you for contacting Mozilla Support. We are happy to help. Currently if I open the Network tool in Firefox the network traffic [HTTP Headers] are only captured on the active page by default and if I refresh the page then the traffic does not stay. What I have been doing to capture is using Live HTTP Headers, but it depends on the extension if you keep logs.

However you can turn it on within as well Mozilla Developer Network has instructions here: https://developer.mozilla.org/en-US/d.../HTTP_logging

# Quit out of Firefox if it's running.
  1. Open a new shell. The commands listed here assume a bash-compatible shell.
  2. Copy and paste the commands in Figure 3 into the shell. Make sure to hit enter after each line.
  3. Reproduce the problem you're debugging.
  4. When the problem has been reproduced, exit Firefox and look for the generated log file, which you can find at /tmp/log.txt.
  • Figure 3 is in the article

And since you are a linux user you may enjoy the developer toolbar, its pretty neat https://developer.mozilla.org/en-US/d.../GCLI

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (2)

more options

Ausgewählte Lösung

Hi kevinoid,

Thank you for contacting Mozilla Support. We are happy to help. Currently if I open the Network tool in Firefox the network traffic [HTTP Headers] are only captured on the active page by default and if I refresh the page then the traffic does not stay. What I have been doing to capture is using Live HTTP Headers, but it depends on the extension if you keep logs.

However you can turn it on within as well Mozilla Developer Network has instructions here: https://developer.mozilla.org/en-US/d.../HTTP_logging

# Quit out of Firefox if it's running.
  1. Open a new shell. The commands listed here assume a bash-compatible shell.
  2. Copy and paste the commands in Figure 3 into the shell. Make sure to hit enter after each line.
  3. Reproduce the problem you're debugging.
  4. When the problem has been reproduced, exit Firefox and look for the generated log file, which you can find at /tmp/log.txt.
  • Figure 3 is in the article

And since you are a linux user you may enjoy the developer toolbar, its pretty neat https://developer.mozilla.org/en-US/d.../GCLI

more options

Thanks guigs2, that's exactly what I wanted to know!