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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.0a3 and above