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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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