Field Value Validation Examples in Proxy Settings Policy
The following are valid and invalid field value examples for ProxyBypassList, ProxyServer, and ProxyPacUrl in the ProxySettings policy.
Proxy Bypass List
Valid:
*.example.com | Matches all subdomains of example.com |
localhost | Matches local hostname |
127.0.0.1 | Matches loopback IP |
[::1] | Matches IPv6 loopback |
*internal.net | Matches any subdomain ending in internal.net |
192.168.1.10:8080 | Matches specific IP and port |
Invalid:
http://*.example.com | Protocols are not allowed |
example.com/* | Paths or slashes are not supported |
regex:.*example\.com | Regex is not supported |
*.*.com | Wildcards can't be stacked like this |
foo.*.com | Wildcards not allowed in middle of domain label |
Proxy Server
Valid:
proxy.example.com:8080 | Uses this proxy for all schemes |
http=proxy1.com:80;https=proxy2.com:443 | Per-scheme configuration |
direct:// | Disables proxy |
socks5://proxyhost:1080 | Valid SOCKS5 proxy with scheme |
192.168.1.100:3128 | IP-based proxy |
Invalid:
http://proxy.example.com:8080 | Do not include scheme in plain format (unless using per-scheme form) |
proxy.example.com | Missing port (may be invalid depending on context) |
https=;http= | Incomplete mapping |
proxy.example.com: | Trailing colon without port |
ftp=proxy1.com;https://proxy2.com | Mixed format or invalid scheme usage |
Proxy PAC Url
Valid:
http://example.com/proxy.pac | Standard PAC file URL |
https://proxy.example.net/autoconfig.pac | Secure PAC file URL |
data:application/x-ns-proxy-autoconfig;base64,... | Inline PAC script in data URI format |
Invalid:
ftp://example.com/proxy.pac FTP protocol not supported file:///C:/proxy.pac Local file paths are invalid http://example.com/proxy.pac/extra URL must point directly to .pac file, not a subpath proxy.pac Relative URLs are not allowed data:text/plain;base64,... Wrong MIME type; must be application/x-ns-proxy-autoconfig
For any additional queries or assistance reach us at https://ulaabrowser.zohodesk.com/portal/en/newticket
Want to share your feedback? Write to us at https://ulaa.com/feedback
Related Articles
DevTool Policy - What is it?
The DevTool Policy blocks access to browser developer tools. When this policy is enabled, users will not be able to open Inspect Element or any developer tools—no matter how they try to access it. This includes: Keyboard shortcuts (like F12 or ...Watermark Policy - What is it?
The Watermark Policy allows organizations to apply a watermark when users print content using the browser. This helps discourage unauthorized printing and adds a layer of traceability. You can customize the text in the watermark (like your company ...Browsing Data Policy - What is it?
Browsing Data Policy lets you control whether browser history is retained or automatically cleared in Ulaa for selected user groups. Example: If you want browser history to be cleared every time someone in the finance team closes the browser, you can ...How to enable Location Tracking Policy?
You can use this policy to control if websites can access users' location while using the Ulaa browser. To enable it, follow the steps given below: Sign in to your Ulaa Admin Console. Click Switch to the Organization on the top right corner (skip ...Device Sensor Policy - What is it?
The Device Sensor Policy controls whether websites can access your device’s sensors, such as motion sensors and orientation data, when browsing through Ulaa. This helps protect privacy and prevent unauthorized use of sensitive device information. You ...
