Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2019.4.23f1
2020.3
2021.1
2021.2
Issue ID
1335054
Regression
No
[WebGL] Not all ResponseHeaders are returned when using UnityWebRequest
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Make a WebGL build
3. Open the built Player in a browser
4. In the Player, click o button labeled "UnityWebRequest"
5. Inspect the logs in the Developer Console (can be accessed with F12 shortcut)
6. Inspect the response in the Network tab
Expected result: All Response Headers are returned by UnityWebRequest.GetResponseHeaders function
Actual result: Only "content-type" and "date" response headers are returned
Reproducible with: 2018.4.35f1, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
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
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Resolution Note:
Turned out to be an issue with the Customer's server setup. Nothing to do with our UnityWebRequest or WebGL implementation.