Search Issue Tracker

Won't Fix

Votes

1

Found in

2018.4

Issue ID

1266559

Regression

No

Proxy bypass list is not honored neither by UnityWebRequest nor by System.Net.Http

When using proxy bypass in Windows proxy settings, it is not honored by UnityWebRequest or System.Net.Http when run on Universal Windows platform.

To reproduce:

1. In the Windows "Change Proxy Settings" (just search "proxy" in Start menu or top-level Settings window), there's a Manual Proxy Setup section to configure your client proxy settings:
• Turn "Use a proxy server" On
• Set "Address" to some dummy IP: 192.168.0.1 (don't actually need a proxy server)
• Set "Port" also to a dummy value: 8888
• In the edit box below you specify the "exclusion" (bypass) list, I use something like this: https://unity3d.com;*.unity.com;*.bing.com;*.youtube.com;*microsoft.com;*.google.com;*.googleapis.com
• Check the "Don't use proxy server for local addresses check"

To test a web request (using Unity or .NET) call the APIs to perform a basic HTTP request to some well known domain, e.g. www.github.com and then get the Response. If you enable the Proxy (flip the switch "On") this call should fail with a either a timeout or "server not found" exception. If you then add the requested site to the bypass list, then the web request should now succeed. If you see this behavior, it means the WebRequest API is actually using your windows settings.

However, if the 1st case succeeds the API isn't using the Proxy address, and if the 2nd case fails it means the API isn't using your Bypass list.

  1. Resolution Note (2020.2.X):

    UWP applications are not allowed the system proxy bypass list, so we cannot honor it. Regular .NET UWP applications (made without Unity) suffer from the same issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.