$cookies doesn't represent current state of document.cookie

[amaltson]

In an $http login call that we make, the resulting header has a Set-Cookie. While the cookie does get set in the browser, i.e. I can see it in document.cookie, it doesn't make it's way to $cookies.

Below is the response header setting the cookie:

And here is document.cookie indicating the cookie exists but $cookies doesn't see it.

The strangest thing is on the next Angular action I take, $cookies has the cookie. The example above is already wrapping the $cookies check in a $timeout to give the browser time to digest.

The workaround right now is to parse document.cookie and set $cookies manually, but this is super hacky.

[kevinjamesus86]

The $cookies service uses $browser.addPollFn to watch for cookie changes ( which runs at 100ms intervals ) and is likely the reason for this behavior. If you increase your $timeout delay to 100ms you will be able to access the cookie from $cookies.

With that said you could use $browser.cookies() directly as it will return a hash of all cookies at the time of the call. If you're used to using the $cookieStore service keep in mind that the former will not deserialize the cookie values for you. I am not sure if the ng team would recommend this but.. yeah, it is an option.

[kevinjamesus86]

@amaltson Alternatively, you could register an http interceptor to update the $cookies service with the cookies at the time of the response: https://gist.github.com/kevinjamesus86/ed559abea9e58bfd3d69. At best this will ensure that when you check $cookies in an http callback it'll be up to date.

[jelling]

+1 for fixing this

[wilk]

Up!

Faced the same problem, solved with $browser.cookies().