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
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.
-
lami
Feb 18, 2015 09:51
I've got the same problem. WWW post works in Chrome (40.0.2214.111 m) but does not in Firefox (35.0.1) and IE 11.
Captured request with Fiddler:
POST http://172.17.43.90:7788/ HTTP/1.1
Host: 172.17.43.90:7788
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-length: 115Content-Length: 69
X-Unity-Version: 5.0.0f2MyBodyData
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #679397