Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.3.18f1
Issue ID
1365107
Regression
No
Timeout value does not propagate when using a DelegatingHandler as the main HttpClient handler
1. What happened
Timeout value does not propagate when using a DelegatingHandler as the main HttpClient handler
2. How can we reproduce it using the example you attached
- Open Assets/Scenes/SampleScene.unity3d
- Enter play mode
- Error will be thrown after 100 seconds to indicate request has timed out
- The end point only responds after 600 seconds and we have set a timeout of 310 seconds
- The bug is likely triggered by using a DelegatingHandler as tthe main handler for the HttpClient instance
Expected result: Console logs a timeout error after 310 seconds
Actual result: Console logs a timeout error after 100 seconds
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a12
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b16
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.26f1