Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.5.0a5
Issue ID
587345
Regression
No
WWW object in Unity Editor cannot communicate with servers that compress their data streams
The WWW object, when running in the Unity Editor, passes a wide-open Accept header (value /) and does not include the Accept-Encoding header.
The HTTP specification states that failing to include an Accept-Encoding header indicates that the client can accept all encodings.
As a result, the crossdomain.xml file is sent to Unity gzipped/compressed, which our WWWCurl object cannot handle. It treats the data as garbage and throws an error indicating that Unity could not retrieve the crossdomain.xml file.
This prevents all WWW requests from working on web servers that serve compressed/gzipped content; this is most high-volume websites out there today.
This is a problem for all platforms that use curl (Unity editor, standalone platforms).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment