Use FULL potencial of FoxyProxy*
Well you know... this project is awesome, thankyou so much!
Now let's get to the point.
I'm on a LAN that uses Websense as a barrier, and I got a proxy same old story from many others... I got a decent knowdelage of regex, but even so I just can't figure out how bypass this... If you're kind to help me I'll do a step by step instructive so others can learn.
I would like to give you the full scenario:
Home: ADSL with static IP + Secure Proxy
Work: Damn fas internet connection + websense
Latest Firefox v2.x
Latest FoxyProxy*
Not every site is blocked by websense so, I need to MANUALLY add sites that are blocked, since aren't reflected in the URL (would be phenomenal if FoxyProxy* detects redirects to certain IP).
Here's a pseudo code to achieve the goal:
if (is localhost || is 127.0.0.1 || company pages) {
Don't use proxy
} elseif (pages don't have restriction) {
Use company proxy
} elseif (pages are restricted) {
Use my own proxy
}
But everytime I try a different configuration, a message shows up telling me that another rule block the rule I've try to add...
Please help, I'm stuck in here... and I've tryed all the week.
Thankyou in advance
--
Edit: "Typo" Corrected the original name of the extension.
Hi, Yes, FoxyProxy (not
Hi,
Yes, FoxyProxy (not FireFoxy) is designed for specifically what your pseudocode describes. I'll post a tutorial for you in this thread this weekend.
Eric
Ohh Sorry!!!
Ohhh God!!!
I feel so stupid and ashamed!!! prior this post I was browsing google's images for "Firefoxy" (see it for yourself)... oh what a dumb-a*s.
So, sorry man...
Hope don't feelt offended by my stupidity!
No problem about the name. I
No problem about the name. I didn't have time to write the tutorial for you because I wrote a bunch of other documentation for FoxyProxy instead (including this, this and this, as well as updated all the screenshots, updated the FAQ, etc.
Right now what you want to do isn't straigtforward in FoxyProxy, but it will be in the next release or two... simply a matter of checking a checkbox. But for now, here's what you need to do. Note that there is more than one way to solve this.
Define two proxies in FoxyProxy. Let's call one OFFICE and the other HOME. Place HOME above OFFICE. Leave the DEFAULT proxy alone at the bottom of the list. Ensure FoxyProxy is set to "Use proxies based on their pre-defined patterns and priorities".
Here's how to define the patterns for each proxy. Using comments in your pseudocode:
if (is localhost || is 127.0.0.1 || company pages) {
Don't use proxy /* Define blacklist patterns for these in both HOME and OFFICE. That way those URLs will be handled by DEFAULT (which should be set to DIRECT; i.e., no proxy) */
} elseif (pages don't have restriction) {
Use company proxy /* define the whitelist wildcard pattern * on proxy OFFICE, which means proxy everything */
} elseif (pages are restricted) {
Use my own proxy /* Enable QuickAdd and configure it to add patterns to HOME when triggered (alt-f2). As you browse the web, use QuickAdd to define whitelist patterns. These automatically get added to HOME. You can even set QuickAdd to auto-reload the page through HOME after you press Alt-F2. */
}
Read how to define patterns here.
You might also find this interesting:
In the FAQ, read the questions How can prevent proxy use on my intranet (local network)? and How can prevent proxy use on my intranet (local network) AND on my local computer (127.0.0.1)?
The next release or two will have a checkbox on each proxy which will say something like "Don't use this proxy for localhost/127.0.0.1" and another which says "Don't use this proxy for plain host names". This will make things a lot easier for you and other people who ask related questions.
Please let me know how it goes for you,
Eric
Or better yet, may be a
Or better yet, may be a (optional) icon for desired proxys, when clicked URLS loaded through are showed... clicking a urls brings up a msgbox with a dropdown list of the proxys (to add it as a black/white listed).
You should use the Logging tab for this. It shows which URLs loaded through which proxies.
As for the regex help, I'm not a regexp expert, but I would break that expression into 2 or 3 different patterns. It will be much easier to write.