Search Issue Tracker
Fixed
Fixed in 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Votes
2
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-130882
Regression
Yes
PROTOCOL_ERROR exception occurs when posting a large blob through AWS ALB
How to reproduce:
1. Open the “2542400 - HTTP2 issue.zip“ project
2. Open the “SampleScene”
3. Enter Play Mode
4. Wait a minute and observe the Console
Actual result: “Curl error 92: HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)” error is thrown
Expected result: “Got response 400 HTTP/1.1 400 Bad Request“ info log is thrown
Reproducible in: 6000.3.0a5 (36d7e9fd6645), 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Not reproducible in: 6000.0.65f1, 6000.3.0a4
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Note: The issue might be inconsistent to reproduce; however, in 6000.3.0a4, the issue consistently is not reproducible
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
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1