Response Headers Blank in 1.4.9?

[mcblum]

I've tried every Google search and server-side fix I can think of. For whatever reason, the response.headers object is always blank in my http interceptor. Here is the response from the server:

Access-Control-Allow-Credentials:true
Access-Control-Allow-Origin:http://site.url
Authorization:Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJI

Here is what I get when I log the response:

config: Object
    headers: Object
        Accept: "application/json, text/plain, */*"
        Authorization: "Bearer eyJ0eXAiOiJK..."
        __proto__: Object
        method: "GET"
        paramSerializer: (t)
        transformRequest: Array[1]
        transformResponse: Array[1]
        url: "http://api.url/admin/pages"
        __proto__: Object
        data: Object
            pages: Array[6]
            __proto__: Object
        headers: (n)
            arguments: (...)
            caller: (...)
            length: 1
            name: ""
            prototype: Object
            __proto__: ()
            <function scope>
    status: 200
    statusText: "OK"

I've tried everything and so I decided to submit an issue. Thanks for your help, and thanks for Angular.
Matt

[Narretz]

I see response headers there. This is a bit thin to act on it.

[mcblum]

Here are all of the response headers I'm seeing in the Chrome dev console as well as the OPTIONS call. Just let me know what else you need and thanks for such a quick response.

The pre-flight request headers:

Accept:*/*
Accept-Encoding:gzip, deflate, sdch
Accept-Language:en-US,en;q=0.8,de;q=0.6,es;q=0.4,pt;q=0.2
Access-Control-Request-Headers:accept, authorization
Access-Control-Request-Method:GET
Cache-Control:no-cache
Connection:keep-alive
Host:api.url
Origin:http://site.url
Pragma:no-cache
Referer:http://hoshi.naitonalmachine.co/settings
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36

The pre-flight response headers:

access-control-allow-credentials:true
access-control-allow-headers:ACCEPT, AUTHORIZATION
access-control-allow-methods:GET, POST, PUT, DELETE
access-control-allow-origin:http://site.url
Access-Control-Expose-Headers:Authorization
Allow:GET,HEAD,POST,PUT,PATCH,DELETE
Cache-Control:no-cache, private
Connection:Keep-Alive
Content-Length:0
Content-Type:text/html; charset=UTF-8
Date:Mon, 25 Jan 2016 19:40:55 GMT
Keep-Alive:timeout=5, max=96
Server:Apache
Set-Cookie:laravel_session=eyJpdiI6IkU5MzVseGpSZFRhRGJQclwvR3F5N1RRPT0iLCJ2YWx1ZSI6InAreW5WVXFmUUlSQXhMM3d6NERITktsbEk2NTZZbWRucDlpckpNdHBMMWYyTGszaWRabEZqbU1GMjdpbFRNT2NaSURqMjliMGVrNStMMmROWTlFaHNRPT0iLCJtYWMiOiIwZWE0OGE5ODNhNGZmOGUxZGJiNzEyNzAxYTMxMWZhNTM2NjQ5NDAwMjNmNmMwNTVmMzcwMjI1ZGI0NjBhYTA1In0%3D; expires=Mon, 25-Jan-2016 21:40:55 GMT; Max-Age=7200; path=/; HttpOnly
Vary:Origin
X-Powered-By:PHP/7.0.0

The GET request headers:

Accept:application/json, text/plain, */*
Accept-Encoding:gzip, deflate, sdch
Accept-Language:en-US,en;q=0.8,de;q=0.6,es;q=0.4,pt;q=0.2
Authorization:Bearer eyJ0eXAiOiJ....
Cache-Control:no-cache
Connection:keep-alive
Host:api.url
Origin:http://site.url
Pragma:no-cache
Referer:http://hoshi.naitonalmachine.co/pages
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36

The GET response headers:

Access-Control-Allow-Credentials:true
Access-Control-Allow-Origin:http://site.url
Access-Control-Expose-Headers:Authorization
Authorization:Bearer eyJ0eXAiOiJKV1QiL... 
Cache-Control:no-cache
Connection:Keep-Alive
Content-Length:6405
Content-Type:application/json
Date:Mon, 25 Jan 2016 19:40:55 GMT
Keep-Alive:timeout=5, max=95
Server:Apache
Set-Cookie:laravel_session=eyJpdiI6Ik04WWVvRHhqNkk4cSswbDRpWkZYbVE9PSIsInZhbHVlIjoiRzhLZlFWSkdvWlwvZVRvWVl2bnZTSVJQNDRZYkpyQjdtdjJCVXV4XC9vSzlBYXZ3dmlqZXhkZnFrMGhvYlNRSUhMbnNvXC85XC9IWnhHRUpMMVZ1enhiZmFnPT0iLCJtYWMiOiIxYzYxZDUwYTBmMGMwOGM4YTYxMjI0YzM2YWQzZWNiOWE3MWM3M2VmZjcxMjQxZDQ0ZGQ0OTA5MzFkMTU0NTUyIn0%3D; expires=Mon, 25-Jan-2016 21:40:55 GMT; Max-Age=7200; path=/; HttpOnly
Vary:Authorization,Origin
X-Powered-By:PHP/7.0.0

My interceptor:

 $httpProvider.interceptors.push(function ($q, $localStorage, $injector) {

            return {
                // outgoing, append the header unless excluded
                // domains match
                'request': function (config) {

                    var excludedDomains = [
                        'mandrillapp.com',
                        's3.amazonaws.com'
                    ];

                    var addHeaders      = true;

                    angular.forEach(excludedDomains, function(value) {
                        if(config.url.includes(value)) {
                            addHeaders  = false;
                        }
                    });

                    if($localStorage.token && addHeaders) {
                        config.headers['Authorization'] = 'Bearer ' + $localStorage.token;
                    }

                    return config;
                },

                // 200 response, parse new token
                'response': function (response) {
                    console.log(response);
                    return response;
                },

                // error, redirect to login page
                'responseError': function(rejection) {

                    // if an error code, check to see if user needs to re-auth
                    if(rejection.data) {
                        if(rejection.data.error == "token_expired" ||
                            rejection.data.error == "token_not_provided" ||
                            rejection.data.error == "user_not_found" ||
                            rejection.data.error == "token_invalid") {

                            $localStorage.$reset();
                            $injector.get('$state').go('login');
                        }
                    }

                    // still return the errors for in-app error handling
                    return $q.reject(rejection);
                }

            };

        });

What I see when I log 'response':

config: Object
    headers: Object
        Accept: "application/json, text/plain, */*"
        Authorization: "Bearer eyJ0eXAiOiJK..."
        __proto__: Object
        method: "GET"
        paramSerializer: (t)
        transformRequest: Array[1]
        transformResponse: Array[1]
        url: "http://api.url/admin/pages"
        __proto__: Object
        data: Object
            pages: Array[6]
            __proto__: Object
        headers: (n)
            arguments: (...)
            caller: (...)
            length: 1
            name: ""
            prototype: Object
            __proto__: ()
            <function scope>
    status: 200
    statusText: "OK"

As far as what response.headers contains, I don't see any of the corresponding response headers. I thought some of them were visible by default, but I'm really confused as to why when specifying Access-Control-Expose-Headers: Authorization that the Authorization response header doesn't get passed into response.headers.

Let me know what you need and once again thank you for addressing this.
Matt

[gkalpak]

response.headers is a getter function. You won't see much, unless you call it.
Have you tried calling it (either with a header name as argument or with no arguments to get all headers) ?
What do you get ?

[mcblum]

I feel like an idiot. Why I couldn't tell it was a function when it literally says 'function' beneith it, I do not know. All is fixed, non-issue can be closed, thank you for your help @gkalpak.