Open Bug 1323823 Opened 8 years ago Updated 2 months ago

Firefox trying to DNS resolve a Kerberos protected domain, even if using a proxy

Categories

(Core :: Networking: Proxy, defect, P5)

45 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: cousin.sebastien, Unassigned)

Details

(Whiteboard: [necko-backlog])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce:

Firefox on windows 7, using system parameters for proxy.
When i try to access a Kerberos protected page (through a proxy), i can see a DNS request for the server FQDN.



Actual results:

When looking network trafic with wireshark, I can see the client ask for the page, the server answers it's waiting for Negotiate auth.
The client then tries to resolve the server FQDN.
If the DNS gives answer, Kerberos trafic occurs, the system gets the TGS and the page is loaded.
If the DNS does not answer, the HTTP/401 is displayed, and nothing happens after the DNS request failure.

The same operation with Internet Explorer does not make any DNS request, and does the Kerberos usual traffic.


Expected results:

Firefox should not ask for any DNS resolution, as it is using a proxy.

This "bug" (feature ?) seems pretty similar to this one : https://bugzilla.mozilla.org/show_bug.cgi?id=890717
Component: Untriaged → Networking: DNS
Product: Firefox → Core
Whiteboard: [necko-backlog]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5

Moving bug to Core/Networking: Proxy.

Component: Networking: DNS → Networking: Proxy
You need to log in before you can comment on or make changes to this bug.