Closed Bug 464402 Opened 16 years ago Closed 9 years ago

XMLHttpRequest null getResponseHeaders() after following 302

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: marius_schilder, Unassigned)

Details

(Whiteboard: [necko-backlog])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081111 Minefield/3.1b2pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081111 Minefield/3.1b2pre Do synchronous XHR to a 302 to a page within the same domain. The XHR readyState goes to 4, responseText is populated but no getResponseHeaders(). A XHR within domain w/o a 302 does return the expected headers. Reproducible: Always Steps to Reproduce: 1. XMLHttpRequest a page that 302s within domain 2. Observe getResponseHeaders() is null 3. Observe readyState == 4 and responseText is not empty Expected Results: HTTP headers of the fetch after the 302. Regression or new. 3.1b1 did not do this.
Component: General → Networking: HTTP
Product: Firefox → Core
QA Contact: general → networking.http
Version: unspecified → Trunk
Whiteboard: [necko-backlog]
I suspect this ticket can be closed. I can't replicate the issue on today's nightly. For both sync and async XHRs, getAllResponseHeaders() returns the same headers for a 302 response that a direct request to the final document does.
Flags: needinfo?(bugs)
Feel free to resolve as worksforme. If there are still issues, one can always reopen the bug or file a new one.
Flags: needinfo?(bugs)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.