search

xiongtong3 / switchy

Automatically exported from code.google.com/p/switchy
0 stars 0 forks source link

Better OSX Support #105

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,

The OSX support is great and very welcome.

But!

Is there some way to isolate the effect of using the proxy, so that it only 
affects Chrome. The way it is currently implemented is to change the 
network settings for the whole system- and so all other programs that I am 
using (like Safari, terminal etc) are forced to use proxy settings which I 
really only want a particular Chrome session to use.

I think that Firefox on osx handles this correctly (in contrast to Safari)- the 
proxy settings are private to Firefox and do not touch the system settings.

I appreciate if the reason this was implemented this way is to do with a 
Chrome technical issue. Certainly, the current implementation does work- 
but I think it should be preferred, if possible, for the proxy settings to only 
affect the way Chrome works and leave the system settings alone (or at 
least it should be optional!).

kind regards,

Original issue reported on code.google.com by peterbar...@gmail.com on 24 Feb 2010 at 7:05

GoogleCodeExporter commented 9 years ago 
I second this request/issue. The whole point of using Switchy is so that I can 
set a proxy for Chrome *only* and not for the rest of my OS. If I wanted to do 
that, I'd just use the Network PreferencePane proxy settings...

Original comment by ari...@gmail.com on 20 Aug 2010 at 3:19

GoogleCodeExporter commented 9 years ago 
Google setup Chrome to do the opposite of what Firefox or any product using 
Mozilla (Chrome uses Webkit (Safari))'s base does and use the System's proxy 
you can find under Network in System Preferences. Not so much of an issue 
because the SystemConfig API is well known, documented and winds up being much 
easier for the average/most users to have configured/be configured since it can 
be done automatically/workgroup/etc.

That being said, I did some dumps on the plugin part of iProxy to see the NSAPI 
stuff going on and it looked pretty hackish--grepping a command for settings, 
etc. It seems like most of us, regardless of how often/many, wind up having 
issues. 

I'm not sure if Chrome will implement some type of hook or API feature to 
control the proxy, germane to how Firefox works their tor plugin. Only issue 
being that you can't bypass the DNS portion (so using pure tor is buggy w/o the 
modified bin/dylib_preloading/etc)

Original comment by atr000 on 4 Sep 2010 at 9:28

GoogleCodeExporter commented 9 years ago 
i third this request. Firefox can do it.

Original comment by m...@missingremote.com on 3 Jun 2011 at 11:19