Bug Tracker

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#11624 closed bug (duplicate)

CORS support: xhr.getResponseHeader('non-simple-header') returns null on Firefox even when header is one of the Access-Control-Expose-Headers.

Reported by: [email protected] Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.7.2
Keywords: Cc:
Blocked by: Blocking:


Specific use case where this was confirmed:

My site domain (e.g. domain.com) is calling my API subdomain (e.g. api.domain.name) to POST data via ajax that results in a 201 response containing a Location header value. 'Location' is not a simple header, so it is listed as required by CORS as one of the Access-Control-Expose-Headers.

The Location header value *is* accessible with jQuery via xhr.getResponseHeader('Location') on Chrome (v18) but *NOT* on Firefox (v11). On Firefox, null is consistently returned. Note I am able to access the Location header value on Firefox if I use the native XMLHttpRequest API.

I haven't had a chance to test on any other browsers.

Change History (3)

comment:1 Changed 11 years ago by anonymous

After some investigation I see from the source that jQuery calls nativeXhr.getResponseAllHeaders() to build the header list used by jqXhr.getResponseHeader("") and that the native getResponseAllHeaders() function is completely broken on Firefox when invoked in a CORS context. So I can see how jQuery's hands are somewhat tied here, as alluded to at http://bugs.jquery.com/ticket/10338.

It might be worth adding to your documentation how to access 'non-simple-headers' since the patch you suggest only provides support for simple headers.

comment:2 Changed 11 years ago by dmethvin

Resolution: duplicate
Status: newclosed

comment:3 Changed 11 years ago by dmethvin

Duplicate of #10338.

Note: See TracTickets for help on using tickets.