X
點擊此處開啟此網站的行動版。

技術支援討論區

Can the Network Monitor preserve its log upon navigation?

已張貼

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

由 kevinoid 於 修改

被選擇的解決方法

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

從原來的回覆中察看解決方案 0

額外的系統細節

已安裝的外掛程式

  • Shockwave Flash 11.2 r202

應用程式

  • User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20131215 Firefox/24.0 Iceweasel/24.2.0

更多資訊

guigs 1072 個解決方法 11697 個答案

選擇的解決方法

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

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/docs/Mozilla/Debugging/HTTP_logging] <blockquote> # Quit out of Firefox if it's running. # Open a new shell. The commands listed here assume a bash-compatible shell. # Copy and paste the commands in Figure 3 into the shell. Make sure to hit enter after each line. # Reproduce the problem you're debugging. # 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 </blockquote> And since you are a linux user you may enjoy the developer toolbar, its pretty neat [https://developer.mozilla.org/en-US/docs/Tools/GCLI]

提出問題者

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

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