Proxying subdir/subpath works on Firefox, but not on Chrome

[Stolka]

URL patterns for subdirectories/subpaths works on Firefox, but it doesn't work on Chrome. For example opening https://github.com/foxyproxy/browser-extension using pattern https://github.com/foxyproxy/* (Match/Wildcard) or ^https://github\.com/foxyproxy/ (RegExp) works on Firefox, but not on Chrome. Is this a bug or Chrome-specific limitation?

Thanks.

[erosman]

The code does process pathname in both Chrome and Firefox versions of FoxyProxy.

However, the proxying is done manually by the extension in Firefox, while in Chrome it is passed to the browser as a PAC and handled by the browser.

I have not tested it but if Chrome doesn’t process pathnames, it could be that the browser caches the connection per host. If that is the case, there isn’t much that can be done by the extension.