Search Issue Tracker

Not Reproducible



Found in


Issue ID




[WWW] [iOS] [Android] Status and other keys missing from WWW.responseHeaders on mobile




Priority: 2Necessary for shipping a final release


Severity: 2No workaround

To Reproduce:

1. Play the attached project in editor & click "Header test", notice the printed out responseHeaders.

2. Deploy the same project to iOS or Android notice, that some of the headers are missing. For example there is no Status key on iOS, and even if there is a key value pair for status on android, the Status key itself is null.
(see the attached screenshots)

Comments (3)

  1. 249fab91e9d9e38c69bdd732be6c78df?d=mm


    Jun 19, 2017 12:30

    I ended up moving to BestHTTP library. I would suggest it for anyone having issues with WWW.

  2. F53bd3f72eb170db2eafccbd6407d58c?d=mm


    Feb 16, 2015 12:03

    Same problem here. We ended up testing with the following hack:

    int statusCode = 200;
    if (!String.IsNullOrEmpty (www.error))
    //first three characters hold the three digit statuscode
    statusCode = int.Parse (www.error.substring (0,3));

  3. C21ffe0182f30f699b3b5bae239de799?d=mm


    Feb 13, 2015 06:40

    I am also getting a key/value pair in response headers like this:
    (NULL:HTTP/1.1 200 OK)

    Happens on android, haven't tested on iOS.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.