Open Bug 914088 Opened 12 years ago Updated 3 years ago

Faulty Behaviour when sending POST Requests with Kerberos Authentication

Categories

(Core :: Networking: HTTP, defect, P3)

23 Branch
x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: t.rieder, Unassigned)

Details

(Whiteboard: [necko-backlog][ntlm])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36 Steps to reproduce: The issue only exists when using the following setup: Firefox <= 23.0.1 Windows XP (the issue does NOT exist on Windows 7/8) Web server (in our case IIS) with Integrated Windows Authentication and Kerberos only (no NTLM) 1. the browser sends a POST request (like for a file upload) 2. the server responds with HTTP/401 not authorized Now the browser is _supposed to_ resend the POST request with the authentication header - but it does not. When using NTLM it actually does resend the request - same when using a Windows 7 client. I'm also inclined to believe that Windows XP itself is not the issue as IE, Chrome and Opera work just fine (they also resend the POST request). I have verified the request behaviour using wireshark. Actual results: Due to the lack of a POST request with authorization headers, the request is unsuccessful and something like file upload is not possible when connecting to a website with kerberos authentication enabled under Windows XP clients. Expected results: 1. the browser sends a POST request (like for a file upload) 2. the server responds with HTTP/401 not authorized 3. browser resends the POST request with the authorization header 4. server replies with something like HTTP/201 created
Component: Untriaged → Security
OS: Windows 7 → Windows XP
Hardware: x86_64 → x86
Component: Security → Networking: HTTP
Product: Firefox → Core
I can confirm this behavior with Firefox 42 on Windows 7. This is the same as in in bug 729496.
Whiteboard: [necko-backlog][ntlm]
Priority: -- → P1
Priority: P1 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.