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:
example.com/* | Paths or slashes are not supported |
regex:.*example\.com | Regex is not supported |
Proxy Server
Valid:
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:
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
|
Related Articles
Watermark Policy Configuration and Deployment Guide
The Watermark Policy in Ulaa Enterprise helps organizations protect sensitive information by displaying customizable text or image-based watermarks on specified websites. Dynamic placeholders can be used to automatically display user, device, ...
Download Restriction Policy Configuration Guide
The Download Restriction Policy in Ulaa Enterprise helps organizations prevent unauthorized or risky file downloads by enforcing restrictions based on: File Size Website URL/Download URL MIME Type (File Type) Using this policy, administrators can ...
Upload Restriction Policy Configuration Guide
The Upload Restriction Policy in Ulaa Enterprise helps organizations prevent unauthorized or risky file uploads by enforcing restrictions based on: File Size Website URL/Upload URL MIME Type (File Type) Using this policy, administrators can block ...
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 ...
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 ...