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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment