Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2021.1
2021.1.0a2
Issue ID
1287962
Regression
No
[WebGL] User-Agent header is not unguarded when using UnityWebRequest
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Make a build for WebGL
3. Host the WebGL build
4. Open the built WebGL Player in a browser
5. Open the developer Console (common shortcut F12)
6. Inspect the messages
Expected result: UnityWebRequest doesn't guard the User-Agent header
Actual result: Errors are thrown
Reproducible with: 2018.4.28f1, 2019.4.14f1 (InvalidOperationException), 2020.1.12f1, 2020.2.0b10, 2021.1.0a4 (Refused to set unsafe header "User-Agent")
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.0a3 and above