is possible that WWW eats himself set-cookie header?

Hi there, Im having a problem specific to windows phone...

Im not getting a header in www.responseHeaders, Im seraching for the Set-Cookie, in other platforms like iOS, BB and Android it work OK even on editor (well on windows editor it gets SET-COOKIE)...

The problem is that on device, it seems that the request is not getting any key that is at less a little related to Set-Cookie.


I have setup an ngrok to watch the remote connection, and the response seems to have set-cookie in it... but when it gets to www.responseHeaders there is no set-cookie.


I wonder if you have found this behaviour and how did you solve it?