We need web-based proxy support on foxyproxy because all of the web-based proxies are faster and more reliable than the browser-configured proxies the software is already set to use. If I, for example go to www.zend2.com and then submit www.website.com in the location bar, then click on NoScript, I says "allow zend2.com", but not "allow website.com". This is a serious security issue when using a web-based proxy because if I come across a browser exploiting website, then viruses are loaded onto my computer because I have zend2 allowed. I also use McAfee SiteAdvisor, and I have the same problem. An example of a security problem with SiteAdvisor while running a web-based proxy is if I go to www.zend2.com and tell the web-based proxy to take me to http://www.8screensavers.com/, SiteAdvisor still indicates "green" and if I click on it, it takes me here, however, if I go directly to www.8screensavers.com, the SiteAdvisor bar indicates "red" and when I click on it, it takes me here. This is because the browser thinks I'm browsing www.zend2.com, which in reality, I'm browsing a completely different site, possibly a dangerous site. Again, I am proposing this because of the security issue when using a web-based proxy. I believe we should use the following method:
When the user types an address into the address bar and foxyproxy is configured for a web-based proxy, foxyproxy will send the request to the web-based proxy. When the server replies, foxyproxy will retrieve the data and load it into the browser, however, suppressing the data from loading in through the default connection.
Does anybody think the above method will work? Do you have a better method? Feel free to post here.
Hi, I don't see how that
Hi,
I don't see how that will fix the security issue you're talking about. In any case, support for web-based (CGI) proxies is already on the "to-do" list for FoxyProxy features.
Thanks,
Eric
Reply
It will fix the security issue by telling the the NoScript and SiteAdvisor add-ons what site I'm browsing so the add-ons know when to disable scripts (NoScript) and which sites to retrieve security information about (SiteAdvisor).
Eh, I don't think the URL is
Eh, I don't think the URL is going to change to the non-proxy URL. There's no way for FoxyProxy (or Firefox, for that matter) to really know which URL the web proxy is loading.
Reply
It will know by monitoring what the user types into the address bar (which will be sent to the web-based proxy next). That's why I was asking for foxyproxy to be given the ability to use a web-based proxy.
Hm, I don't really think
Hm, I don't really think that's possible, at least not in a reasonable way. I will investigate further, but that is my gut feeling based on my knowledge of Firefox programming and Firefox extension programming.
When I envision CGI-based proxy support, I mean that foxyproxy will open a new tab/window for a single URL using a CGI proxy.