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
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
- The cogwheel button in the Build History window gets distorted when the Build History window is resized or options are ticked in the toolbar
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.