Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
0
Found in
5.4.1f1
Issue ID
832192
Regression
No
UnityWebRequest does not send set cookies on redirect
Steps to reproduce:
1. Open the attached project
2. Open the Assets/test.unity scene
3. Open Wireshark
4. Filter http traffic
5. Play the scene by pressing the Play button
6. Observe, any new cookies are not sent on a redirect
Expected result: UnityWebRequest should send set cookies on redirect
Actual result: UnityWebRequest does not send set cookies on redirect
Note:
Feature introduced in 5.4
Reproduced with: 5.4.1f1, 5.4.4p3, 5.5.0f3, 5.5.1p4, 5.6.0b9
Fixed in:
2017.3.0a2
Backported to:
2017.2.0b6
Comments (1)
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
vinsonb
Sep 27, 2017 15:44
It appears the "fix" for this issue may have been to use CookieHandler.setDefault, which in my opinion is bad. This can have unintended consequences for native code and plugins that may not be expecting a default cookie manager to be set. I think Unity should track/set cookies on their own instead of setting a default manager.