Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.3f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1188229
Regression
No
UnityWebRequest opens and keeps seperate connections for each request
How to reproduce:
1. Open the attached project
2. Change the IP addresses to yours in the PythonServer/bounce.py and Assets/Request.cs scripts
3. Build the project
4. Open the built Player on other machine
5. Start the python server (python3 PythonServer/bounce.py)
6. On the client machine, keep pressing "Connect"
7. On the client machine, check open network connections (using netstat)
Actual result: The client creates different connection for each request (the connection stays alive).
Expected result: The opened connection has to be closed or the requests have to go through the same connection.
Reproducible with: 2020.1.0a8, 2019.3.0b6, 2019.2.8f1, 2018.4.11f1, 2017.4.33f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment