Search Issue Tracker
Fixed in 5.0.1
Votes
2
Found in
4.5.5f1
Issue ID
647126
Regression
No
WWW returns incorrect HTTP status 100 when POST data is relatively large
To Reproduce:
1. Run /Assets/WebPlayerTemplates/server.js (in the attached project) using node.js.
2. Open the project attached to the post in Unity, play.
3. Click 'Small post', notice that status returns 200.
4. Click 'large post', notice that is 100 returned, even if the server returns 200.
5. Only happens when .postValues members contain more than ~1000 characters.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment