Hi,
I wanted to setup a proxy which proxies everything other than localhost servers. After i realized that wildcards didn't seem to handle port-numbers (e.g., http://localhost:*/* wouldn't mage local servers with explict ports) and given that wildcards also result in plenty of rules, i wanted to switch to regular expressions. Unfortunately, regular expression didn't seem to match at all. While i inittially tried what i really want (^[a-zA-Z]*://(?:[^:@/]+(?::[^@/]+)?@)?(?:localhost|127\.\d+\.\d+\.\d+)(?::\d+)?/.*'), successively simplifying to something like http://127\.0\.0\.1.* or even .* which should match everything didn't trigger a hit (and this was for both blacklist as well as white list rules, case sensitive or insensitive). Any idea what's wrong here? Issue with 3.5 beta which has another JS engine?
btw: my system is linux rhel5.3, just in case ...
Hi, I haven't had time to
Hi,
I haven't had time to test this yet, but will do so soon. I'll re-post with my findings.
Thanks,
Eric
Confirmed. I was able to
Confirmed. I was able to work around the problem by installing FoxyProxy to a new Firefox 3.5b4 profile. I'll try to see if Mozilla is aware of the bug since it appears to be problem with that version of Firefox.
Eric
If you create a new Firefox
If you create a new Firefox profile, this problem disappears. You can reuse your old FoxyProxy settings after creating the new profile by copying foxyproxy.xml from the old profile directory into the new one.
new profile ...
thanks for the investigation.
One question though: Is this a temporary workaround as either FF3.5 and/or foxyproxy will eventually fix the bug or is it to stay? Given that creating a new profile is rather painful if you have a lot accumulated context (plugins, settings, cookies, stored password, ...) in a given profile, i'm trying to make up my mind whether to plunge for the pain or wait for a while :-)
Sorry, I don't know.
Sorry, I don't know.