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
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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
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.