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
- Localization Group Rules bypasses Locale logic when SharedGroup asset provided
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
This is a duplicate of issue #955264