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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment