### Preamble Proxy bypass/override feature is provided in Firefox (via Network Settings UI and extension [proxy.settings](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/proxy/settings) API), and in Chrome (via extension [chrome.proxy](https://developer.chrome.com/docs/extensions/reference/proxy/#bypass-list) API). There are a number of inconsistencies between Firefox & Chrome implementation of proxy bypass list. - Host matching In Chrome, `xyz.com` only matches the exact host while in Firefox it matches any host containing the string. - PAC As posed in [Inconsistency: Proxy Bypass list](https://github.com/w3c/webextensions/issues/339), Chrome doesn't apply the bypass list to the PAC which limits its versatility. Firefox's approach is more beneficial (please keep the feature). - Array vs comma-separated string Not that important though 📌 The **Host matching** inconsistency is the subject of this bug filing. ### Purpose Besides the inconsistency with Chrome, the Chrome pattern matching has additional versatility. > Examples: `"foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99", "https://x.*.y.com:99".` It enables specific rules to include or exclude subdomains. Hosts often use subdomain to point to a different server, or different location altogether. For example,`api.xyz.com` may be in a different country comparing to the primary `xyz.com` server. Location based servers are also common e.g. `en.xyz.com, de.xyz.com` etc Furthermore, subdomains may serve different type of service comparing to the main domain server. The aforementioned situation is more common with proxy servers where often subdomains may point to a proxy-server while the main domain points to a web-server. **Note:** In Firefox, the proxy override can match TLD which is quite useful e.g. `.fr` (please keep the feature). Chrome documentation does not show TLD matching.
Bug 1810738 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Preamble Proxy bypass/override feature is provided in Firefox (via Network Settings UI and extension [proxy.settings](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/proxy/settings) API), and in Chrome (via extension [chrome.proxy](https://developer.chrome.com/docs/extensions/reference/proxy/#bypass-list) API). There are a number of inconsistencies between Firefox & Chrome implementation of proxy bypass list. - Host matching In Chrome, `xyz.com` only matches the exact host while in Firefox it matches any host containing the string. - PAC As posed in [Inconsistency: Proxy Bypass list](https://github.com/w3c/webextensions/issues/339), Chrome doesn't apply the bypass list to the PAC which limits its versatility. Firefox's approach is more beneficial (please keep the feature). - Array vs comma-separated string Not that important though 📌 The **Host matching** inconsistency is the subject of this bug filing. ### Purpose Besides the inconsistency with Chrome, the Chrome pattern matching has additional versatility. > Examples: `"foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99", "https://x.*.y.com:99".` It enables specific rules to include or exclude subdomains. Hosts often use subdomain to point to a different server, or different location altogether. For example,`api.xyz.com` may be in a different country comparing to the primary `xyz.com` server. Location based servers are also common e.g. `en.xyz.com, de.xyz.com` etc Furthermore, some subdomains may serve different type of service comparing to the main domain server. The aforementioned situation is more common with proxy servers where often subdomains may point to a proxy-server while the main domain points to a web-server. **Note:** In Firefox, the proxy override can match TLD which is quite useful e.g. `.fr` (please keep the feature). Chrome documentation does not show TLD matching.
### Preamble Proxy bypass/override feature is provided in Firefox (via Network Settings UI and extension [proxy.settings](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/proxy/settings) API), and in Chrome (via extension [chrome.proxy](https://developer.chrome.com/docs/extensions/reference/proxy/#bypass-list) API). There are a number of inconsistencies between Firefox & Chrome implementation of proxy bypass list. - Host matching In Chrome, `xyz.com` only matches the exact host while in Firefox it matches any host containing the string. - PAC As posed in [Inconsistency: Proxy Bypass list](https://github.com/w3c/webextensions/issues/339), Chrome doesn't apply the bypass list to the PAC which limits its versatility. Firefox's approach is more beneficial (please keep the feature). - Array vs comma-separated string Not that important though 📌 The **Host matching** inconsistency is the subject of this bug filing. ### Purpose Besides the inconsistency with Chrome, the Chrome pattern matching has additional versatility. > Examples: `"foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99", "https://x.*.y.com:99".` It enables specific rules to include or exclude subdomains. Hosts often use subdomain to point to a different server, or different location altogether. For example,`api.xyz.com` may be in a different country comparing to the primary `xyz.com` server. Location based servers are also common e.g. `en.xyz.com, de.xyz.com` etc Furthermore, some subdomains may serve different types of service comparing to the main domain server. The aforementioned situation is more common with proxy servers where often subdomains may point to a proxy-server while the main domain points to a web-server. **Note:** In Firefox, the proxy override can match TLD which is quite useful e.g. `.fr` (please keep the feature). Chrome documentation does not show TLD matching.
### Preamble Proxy bypass/override feature is provided in Firefox (via Network Settings UI and extension [proxy.settings](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/proxy/settings) API), and in Chrome (via extension [chrome.proxy](https://developer.chrome.com/docs/extensions/reference/proxy/#bypass-list) API). There are a number of inconsistencies between Firefox & Chrome implementation of proxy bypass list. - Host matching In Chrome, `example.com` only matches the exact host while in Firefox it matches any host containing the string. - PAC As posed in [Inconsistency: Proxy Bypass list](https://github.com/w3c/webextensions/issues/339), Chrome doesn't apply the bypass list to the PAC which limits its versatility. Firefox's approach is more beneficial (please keep the feature). - Array vs comma-separated string Not that important though 📌 The **Host matching** inconsistency is the subject of this bug filing. ### Purpose Besides the inconsistency with Chrome, the Chrome pattern matching has additional versatility. > Examples: `"foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99", "https://x.*.y.com:99".` It enables specific rules to include or exclude subdomains. Hosts often use subdomain to point to a different server, or different location altogether. For example,`api.example.com` may be in a different country comparing to the primary `example.com` server. Location based servers are also common e.g. `en.example.com, de.example.com` etc Furthermore, some subdomains may serve different types of service comparing to the main domain server. The aforementioned situation is more common with proxy servers where often subdomains may point to a proxy-server while the main domain points to a web-server. **Note:** In Firefox, the proxy override can match TLD which is quite useful e.g. `.fr` (please keep the feature). Chrome documentation does not show TLD matching. In other words ... ``` .fr = *.fr .example.com = *.example.com ```