Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2020.3.37f1
2021.3.7f1
2022.1.10f1
2022.2.0b2
2023.1.0a4
Issue ID
UUM-9787
Regression
No
Warnings and errors are spammed in the Console when pinging localhost:34999 making it harder to debug
Reproduction steps:
1. Open the “EmptyProject” or any Unity project
2. Open [http://localhost:34999/] in a web browser
3. Observe the Console in the editor
Expected result: No warnings nor errors are logged
Actual result: Warnings and errors are logged
Warning: Sending message header failed (35)
Error: The message header is corrupted and for security reasons connection will be terminated
Reproduced in: 2020.3.37f1, 2021.3.7f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4
Reproduced on: Windows 11, macOS Monterey 12.0.1
Note: 2020.3 reproduced the errors, but not the warnings
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Opening a browser against the player connection port used by the browser is not a supported scenario - it makes no sense to do this. The player connection does not interpret HTTP web requests.
We need to review the ISS customer's issue here, because it's not reflected in this bug.
Resolution Note (2023.1.X):
Opening a browser against the player connection port used by the browser is not a supported scenario - it makes no sense to do this. The player connection does not interpret HTTP web requests.
We need to review the ISS customer's issue here, because it's not reflected in this bug.