Hi,

I suggest to add an option to the AutoAdd function to scan the page title for a certain pattern.

Reason: I tried to use FP to AutoAdd sites that were blocked by a content filter in my network. So always when I hit a blocked site I get a message saying that site is blocked blah blah.
AutoAdd somewhat works for this but I experience a performance hit and sometimes (quite regularly actually) get the error "A script on this page may be busy, or it may have stopped responding. You Can Stop the Script now or you can continue to see if the script will complete. [Stop Script] [Continue]".

I think for some occasions (as with my content filter) it would be sufficient to scan the <title> only. This should be much faster than scanning the whole page.

Thanks,

Smee

Hi,

Actually, QuickAdd is coming in the next release -- it's already finished. It's much better than AutoAdd because it's user-driven... you press alt-f2 on any page and the page's URL gets added to a proxy and optionally reloaded.

...but thanks for the idea.

-eric

One thing which I can't seem to find is whether AutoAdd inserts the URL as a BLACKLISTED site or a WHITELISTED site to the proxy (and where in the priority).

I assume that it and the new feature will work by blacklisting the ORIGNIAL URL for the proxy used? (I have websense producing a known string, and want my corporate proxy to go ahead of my home tunnel in the pattern, but can't seem to configure it and there is no tutorial or FAQ covering it).

Since this is the right forum, a test mode or box where I could type a test URL or string and see which rules it matched (or not - things like typos, zero vs Ohs, etc. are sometimes hard to find especially with complex logic).

Hi,

It adds a whitelist pattern.

No, whitelisting. No one requested the ability to quickly add blacklisted patterns, and I didn't think it would be useful. If you'd find it useful, I can add it. Let me know.

I don't really understand. Are you asking a question? Are you asking for a feature?

Yes, I'd like a feature where I could type a URL and see which proxy it would use. I could keep getting "BLOCKED" notices from our corporate firewall, but I don't want to do that too many times.

The direct out through the firewall is much faster than through the bypass SSH tunnel I use. So when a site is blocked, I'd like it BLACKlisted for the regular corporate firewall, then it can pass through to whatever other proxy I'm bypassing it with. If I change tunnel proxies, I'd have to move the whitelist, but as a blacklist, it would be linked to the problematic proxy.

So far, I haven't gotten AutoAdd to work either way. That is another reason I would like a test section. I have a string which is clear on the "blocked" screen, but it seems to try reloading the blocked screen without adding the original URL anywhere.

And to add, the ability to copy/move/cut/past black/whitelist entries between proxies.

I'm trying to reconfigure it so the autoadd should work, but there is no way of opening two configure boxes, nor of doing a copy-paste.

And maybe a way of highlighting which proxy - on a high speed link the text (which is also rather wide - do you need to say "FoxyProxy:") flashes quickly and returns to "Patterns" rapidly. A configurable tag for each proxy - text, color, attribute would make that much easier.

Apparently the following text doesn't match *Websense* as wildcards for AutoAdd:

I tried several other things based on the strings, but that is why a test-box would help.

I can't get the string to match anything.

You need to match the HTML of the page, not the displayed text. I will add a test-box.

Where would this "tag" appear? And why would switch slower than the statusbar text?

I will add the ability to define whether or not the AutoAdd/QuickAdd pattern in whitelist or blacklist, but not in 2.5.

For now, you can make the AutoAdd pattern be blacklist this way:

• Close all Firefox browsers.
• Open foxyproxy.xml and look for the tag <autoadd>.
• Under <autoadd> is a tag called <match>. Change the isBlackList="false" attribute on <match> to isBlackList="true".

WARNING: there is more than one <match> tag in foxyproxy.xml. Ensure the one you change is under <autoadd> !!!

Thanks for considering the fixes and explaining how to do the blacklist thing.

A custom icon or text with attributes replacing "FoxyProxy: Patterns" in the status bar would be more visible. Right now, all pattern text is yellow, so I have to watch quickly since it is replaced by FP:X or FP:Y with exactly the same color for a fraction of a second. If it flashed red or blue I could tell which proxy it chose.

I don't know what is wrong with my matching because

*ebsense* (either regex or wildcards)

Apparently doesn't match anything in the following HTML:

Or in the actual frame explaining things:

OK, I understand now. This has been asked by others. I will do it as soon as possible.

It appears that AutoAdd is broken in FoxyProxy 2.4.1. I have fixed it for release 2.5, which will be released shortly. It was supposed to have been released today (4 March 2007), but I am working on some last-minute bug fixes.