Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
2
Found in
2020.3
2020.3.14f1
2021.1
2021.2
2022.1
Issue ID
1352501
Regression
No
[WebGL] Request is still redirected when setting UnityWebRequest.redirectLimit to zero on WebGL
How to reproduce:
1. Open the attached project's "case_1352501-Project.zip" Scene labeled "SampleScene"
2. Open the "RedirectTest.cs" script
3. Change the request URI to a redirecting address (preferably set up on local domain to avoid CORS errors)
4. Make a WebGL build
5. Host the built Player on a local webserver (i.e. Apache)
6. Open the Player in a browser
7. Wait for the Player to load
8. Inspect the developer's console (common shortcut F12)
Expected result: Request returns an error that "Redirect limit exceeded"
Actual result: Request is successful
Reproducible with: 2020.3.15f1, 2021.1.16f1, 2021.2.0b5, 2022.1.0a4
Couldn't test with: 2019.4.29f1 (ERR_BLOCKED_BY_CLIENT)
Note:
- Used Apache server when testing and had a ".htaccess" set up with "Redirect 302 <URL>" on the same local domain as 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 importing lightmaps after GI bake
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a11
Resolution Note (fix version 2021.2):
Fixed in 2021.2.19f1