Search Issue Tracker
By Design
Votes
0
Found in
2019.2
2019.2.0f1
2019.3
2020.1
Issue ID
1192159
Regression
No
UnityWebRequest header keys and values not shown correctly when running the project as WebGL build
How to reproduce:
1. Open User's attached "WebGLBugTest.zip" project
2. Load "StandaloneListener" scene
3. Build and Run "StandaloneListener" as Windows Standalone build, leave it running
4. Refocus Unity Editor and load "StandaloneRequester" scene
5. Enter the Play mode
6. Exit the Play mode, Build and Run "StandaloneRequester" as WebGL build
7. Observe "WebGLBugTest.exe" window (which was opened after running "StandaloneListener" Windows build)
Expected result: "KEY:TAGHUB_CONSUMER_KEY" value is shown correctly in "WebGLBugTest.exe" window, for WebGL build part (same as when running "StandaloneRequester" through Play mode)
Actual result: "KEY: Access-Control-Request-Headers" and "VALUE: taghub_consumer_key" appears instead in "WebGLBugTest.exe" window, for WebGL build part
Reproduced with: 2019.2.11f1, 2019.3.0b8, 2020.1.0a9
Could not reproduce with: 2017.4.33f1, 2018.4.12f1 (trying to fix dependency errors causes project to not work anymore)
Notes:
- After running WebGL build, "Unknown Error" shows up on the screen, in the browser window. This doesn't happen when running "StandaloneRequester" through the Play mode
- "StandaloneListener" listens for http requests. It shows results from both "StandalonRequester" running in the Play mode and WebGL build
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 memcpy when using ScreenCapture.CaptureScreenshot with superSize set to zero
- [URP] Package Samples - Missing scripts in Unity 2022+
- [URP][Package Samples] Continuous "Renderer at index _ is missing for camera _" warnings when opening sample scene
- [URP] Package Samples - Missing scripts in Unity 6
- [URP] Package samples - scenes using FirstPersonController not working in Unity 6
Resolution Note:
Not a bug - when custom HTTP request headers are present and request is made to another domain, web browsers must run a CORS OPTIONS preflight check. In such check, the string "taghub_consumer_key" does and should appear as a VALUE, rather than a KEY.