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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.