Search Issue Tracker

Duplicate

Votes

57

Found in

Issue ID

672251

Regression

Yes

WWW POST request on WebPlayer built by Unity 5.0.0f2 creates an invalid request

Webplayer

-

WWW POST request on WebPlayer built by Unity 5.0.0f2 creates an invalid request, therefore servers cannot read the body properly and they receive missing headers.

  1. This is a duplicate of issue #679397

    WWW forms do not work properly in WebPlayer, Unity 5
Log in to vote on this issue

Comments (31)

  1. clever

    Mar 11, 2015 04:53

    Same problem! please fix it's bad for business :)

  2. IsaacMonkimun

    Mar 10, 2015 16:21

    I have the same issue in iOS. Working fine in editor, but doesn't work on iOS.

    "The operation couldn’t be completed. (NSURLErrorDomain error -1012.)"

    Unity version: 5.0.0f4

  3. DarkWindfury

    Mar 10, 2015 15:42

    Same here Unity 5.0.0f4 , works only in Chrome and Opera (latest updates)

  4. ShyRec

    Mar 10, 2015 13:18

    same issue on 5.0.0f4

    Doesn't work on IE and Firefox. Works well on Safari and Chrome.
    No matter Win or Mac os.
    Newest web player.

  5. devluz

    Mar 09, 2015 02:58

    Same problem here. The header is missing the data
    [content-type] => application/x-www-form-urlencoded
    [x-unity-version] => 5.0.0f4

    as well as all custom set headers in firefox. It works fine in chrome. This is a very bad bug hope it is fixed soon

  6. HockeyMarv

    Mar 08, 2015 19:33

    Same here

  7. Erdroy

    Mar 07, 2015 22:22

    Same in 5.0.0f4...
    Just google chrome works... : /

  8. michidk

    Mar 07, 2015 08:57

    Same issure with v5.0.0f4.

    Firefox newest version (just downloaded)

    Works fine in Editor and Chrome.
    But with WebPlayer-Build in Firefox, the Request parameters a null

  9. david_n

    Mar 05, 2015 16:34

    Same issue here with Webplayer and Firefox on OSX Yosemite. It works just fine with Safari and Chrome.

    Unity version : 5.0.0f4
    Firefox version : 36.0

  10. g_a_p

    Mar 03, 2015 10:58

    Same issue with v5.0.0F3 and any browser.

Add comment

Log in to post comment

All about bugs

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

Latest issues

See all new issues