Bugzilla

So in my environment, I can only reproduce this bug with certain addon installed, can't reproduce this issue in a fresh profile. So this is somehow different as Tobias's case (Comment 4).

In my test, after opening inspector, devtools code triggered another request to the site with basic authentication.
In necko, while receiving the request, it didn't add `Authorization` header to the request so we prompt the authentication dialog again after receiving response from the server. We probably need necko team's help to check whether not adding `Authorization` header in this case is expected.

So in my environment, I can only reproduce this bug with lastpass installed, can't reproduce this issue in a fresh profile. So this is somehow different as Tobias's case (Comment 4).

In my test, after opening inspector, devtools code triggered another request to the site with basic authentication.
In necko, while receiving the request, it didn't add `Authorization` header to the request so we prompt the authentication dialog again after receiving response from the server. We probably need necko team's help to check whether not adding `Authorization` header in this case is expected.

I can only reproduce this bug with lastpass is installed, I can't reproduce this issue with a fresh profile in my environment. So this is somehow different from what Tobias has encountered.

In my test, after opening the inspector, devtools code sent a request to the same URL as the first one, which triggered the second auth prompt. I didn't dig into why that was happening, so I'm not sure if that is expected.
In necko, after receiving the request, it didn't add `Authorization` header even if we've filled in the credential in the first prompt. So the authentication dialog prompted again after receiving response from the server.