Search Issue Tracker
Duplicate
Votes
0
Found in
2017.2.0p4
2017.3.0a1
Issue ID
981979
Regression
Yes
"WWW" class forced to send form data using Chunked Transfer Encoding
Reproduction steps:
1. Open "capture.js" using "Node.js"
2. Open "UnityProjectWWW.zip" project with 2017.2 and below
3. Enter Play mode
4. See the output in "Node.js"
5. Open "UnityProjectWWW.zip" project with 2017.3 and above
6. Enter Play mode
7. See the output in "Node.js"
8. See that the second output has "Transfer-Encoding: chunked" (HTTP 1.1) which is not compatible with some servers
Expected Result: 2017.3 and above should have an option to disable HTTP 1.1 chunked transfer encoding for compatibility
Actual Result: 2017.3 and above is forced to use HTTP 1.1 chunked transfer encoding
Reproduced with: 2018.1.0b2, 2017.3.0p2, 2017.3.0b11, 2017.3.0a1*
Did not reproduce on: 2017.2.1p2, 2017.1.3f1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #955264