Search Issue Tracker
Fixed in 5.5.2
Votes
4
Found in
5.4.2p4
Issue ID
861828
Regression
No
[UnityWebRequest] Proxies such as Charles and Fiddler don't show UnityWebRequest requests
Can't view/debug UnityWebRequest HTTP requests because proxies (Fiddler/Charles) can't show the trafic. This does work when using WWW instead however.
To repro:
1) Open attached project
2) Go to Main scene and Test GameObject in hierarchy
3) Set request type to WWW in inspector
4) Run and see HTTP request show in Charles or Fiddler
5) Stop playmode
6) Set request type to UnityWebRequest
7) Run again and see no HTTP request in Charles or Fiddler
Reproduced: 5.4.2p4, 5.5.0f3 Mac and 5.4.0f3 Windows
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
dan-kroymann
Jan 11, 2017 18:36
While researching this issue, I realized that this could potentially mean that if a user's computer is behind a network where a proxy server has to be manually configured, then UnityWebRequests (which currently seem to ignore the system's default proxy) will not work. Could someone from Unity confirm/deny this?