![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Network monitor Tool Bugs
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!
منتخب شدہ حل
You can file bugs on this page: https://bugzilla.mozilla.org/enter_bug.cgi
اس جواب کو سیاق و سباق میں پڑھیں 👍 1تمام جوابات (2)
منتخب شدہ حل
You can file bugs on this page: https://bugzilla.mozilla.org/enter_bug.cgi
Filed my two findings as bugs here: