current community

your communities

more stack exchange communities

Stack Exchange
tour help
stack overflow careers
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 34 down vote favorite
4

I am using $http to make an api call which is sending some custom header like X-Foo. However I can't yet figure out how to read them. Inside the $http({...}).success(function (data, status, headers, config) {...}) function, headers is a function that should give me a hash of all headers but it only shows the header content-type. Is there a way to get the response headers ?

share|improve this question
    
Are you using Firefox? See stackoverflow.com/questions/14188662/…. –  Dhruv Chandna Jun 11 '13 at 7:31
    
No, chrome. Does the FF specific fix work for chrome ? –  Joy Dutta Jun 11 '13 at 15:43
1  
Are the requests being made to a different domain or the same domain? I tested sending the request to the same domain and I am able to see the custom headers. –  Dhruv Chandna Jun 12 '13 at 4:17
2  
You are right, the issue was due to different domains. I could finally get the custom headers to show after I made the server to send the header Access-Control-Expose-Headers. –  Joy Dutta Jun 12 '13 at 17:58
17  
@JoyDutta You should create an answer, so to make this question not listed under "unanswered" tab. –  Ye Liu Jul 11 '13 at 20:37

1 Answer 1

up vote 67 down vote accepted

The custom headers will be visible in same domain. However, for the crossdomain situation, the server has to send Access-Control-Expose-Headers: X-Foo, ... header to make the custom headers visible.

share|improve this answer
3  
Thank you! You saved my night –  JRun May 11 '14 at 20:00
3  
It appears that you must specify the actual header name instead of a wildcard. Access-Control-Expose-Headers:* does not work, but Access-Control-Expose-Headers:Etag does. –  Sam Barnum Jun 20 '14 at 18:00
3  
this did not seem to work for me with angular's $http –  chovy Oct 30 '14 at 22:27
    
Seems that even standard headers don't work with CORS without this workaround. Had to add this: Access-Control-Expose-Headers: Content-Disposition to make the content-disposition header visible in angularjs. –  zszep Mar 5 at 10:26
    
This does work with angular v1.3 –  line-o Mar 18 at 18:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.