Hey, I've come across a problem that the WWW class seems to work correctly in the Unity Editor but not in the Android or the WebGL (using Chrome) builds. I make a request to the server using the WWW class. I get back a response, which's headers I can access through the WWW.responseHeaders. What I need to get is a "Set-Cookie" header and it needs to include "PHPSESSID: ...". Inside the editor, everything works fine. When I use a for loop to go through the WWW.responseHeaders, one of the headers is "Set-Cookie" and it contains "PHPSESSID" plus some other attributes. This can be seen on the following image: However, on android or webgl, the results are different. Set-Cookie header is present but only the returningMinTimer part gets through (is listed with the for loop) as seen on the following picture: Spoiler: Android WWW.responseHeaders Debug.Log Plus 2 more fields (X-Android-Sent-Millis:150... & X-Powered-By: PHP/5.6.30). In WebGL, the WWW.responseHeaders does not contain the "Set-Cookie" header at all. The WebGL debug.log can be seen in the following image: Spoiler: WebGL WWW.responseHeaders Debug.Log What is interesting with the WebGL build however, is that when I use the developers tools and go to the Networking tab to see the requests I sent and look at the header returned to the browser... My request was split into two requests. Originally, the request was supposed to be a POST request. But instead, first an OPTIONS request is sent and then a POST request right afterwards. In the OPTIONS request's response headers, the "Set-Cookie" is missing: Spoiler: WebGL OPTIONS And the POST request DOES not only contain the "Set-Cookie" header but also has the "PHPSESSID" parameter (you can ignore the fact that there are multiple PHPSESSID-s): Spoiler: WebGL POST All of this leads me to believe that the WebGL and Android builds process WWW headers differently from the Unity build. The android version only receives one parameter of the Set-Cookie, while the WebGL build separates the request into two (OPTIONS and POST) and the responseHeaders are taken from the OPTIONS headers. And this is incorrect. Any help would be very much appreciated! Thank you!