Closed Bug 1645128 Opened 5 years ago Closed 5 years ago

Network monitor Tool Replay request

Categories

(DevTools :: Netmonitor, defect)

77 Branch
x86_64
Windows 10
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: judos, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

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.

Actual results:

While editing a request in the network monitor tool it seems that the Authentication header is not sent anymore with the request. In the UI it is however still shown that the Authentication header is sent as part of the request header. However the backend notes that it does not arrive.

Expected results:

Authentication header should be sent normally when request is editted and sent again.

OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Netmonitor
Product: Firefox → DevTools

Thanks for the report!

This sounds like a bug.

Can you please provide a simple test case (an online page or attach a test page) we could use to reproduce the problem on our machines?
That would be great help.

Honza

Flags: needinfo?(judos)

Judos, are you planning to provide a test case?
Or perhaps there is an existing page we could use to reproduce the problem?

Honza

Hey Judos,
Had a look into this. It seems like from your description above, you seem to be looking for the header Authentication: Bearer <token>.
It seems like the header should rather be Authorization: Bearer <token>. See https://swagger.io/docs/specification/authentication/bearer-authentication/.
Please confirm this and if you can see it.

Thanks

Closing this now.
Judos, please feel free to reopen with more info.
Thanks

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.