為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Network monitor Tool Bugs

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 judos

more options

Hi there,

I'm frequently using the network monitor tool as developer. Now I found two bugs:

Gateway timeout: While developing I got a gateway timeout for an endpoint of my current project. In the console this is correctly logged but in the network monitor I don't see anything. This is quite confusing. The console log looks like this:

ERROR Error: "Uncaught (in promise): S: {"headers":{"normalizedNames":{},"lazyUpdate":null,"headers":{}},"status":504,"statusText":"Gateway Timeout","url":"https://myurl.myurl/profil","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://myurl.myurl/profile: 504 Gateway Timeout","error":null}"


Replaying request: Very useful feature, however it seems to have an issue with Authentication headers. When my angular application does a service call it works fine. When I then replay this request I get the response of the backend: 401 you are not logged in. Upon closed inspection I printed out the headers in this response and noted that after replaying the request the header "Authentication: Bearer ...." is missing.

Any hints how to fix these issues?

Also is this the correct space to report issues/bugs? I also found this url: https://github.com/mdn/kuma/issues which i'm not quite sure whether it would be the right space to open tickets for firefox network monitor tool.

Thanks for your help!

Hi there, I'm frequently using the network monitor tool as developer. Now I found two bugs: Gateway timeout: While developing I got a gateway timeout for an endpoint of my current project. In the console this is correctly logged but in the network monitor I don't see anything. This is quite confusing. The console log looks like this: ERROR Error: "Uncaught (in promise): S: {"headers":{"normalizedNames":{},"lazyUpdate":null,"headers":{}},"status":504,"statusText":"Gateway Timeout","url":"https://myurl.myurl/profil","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://myurl.myurl/profile: 504 Gateway Timeout","error":null}" Replaying request: Very useful feature, however it seems to have an issue with Authentication headers. When my angular application does a service call it works fine. When I then replay this request I get the response of the backend: 401 you are not logged in. Upon closed inspection I printed out the headers in this response and noted that after replaying the request the header "Authentication: Bearer ...." is missing. Any hints how to fix these issues? Also is this the correct space to report issues/bugs? I also found this url: https://github.com/mdn/kuma/issues which i'm not quite sure whether it would be the right space to open tickets for firefox network monitor tool. Thanks for your help!

被選擇的解決方法

所有回覆 (2)

more options

選擇的解決方法

You can file bugs on this page: https://bugzilla.mozilla.org/enter_bug.cgi

more options