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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Add comment