Closed GoogleCodeExporter closed 8 years ago
Original comment by Mohamma...@gmail.com
on 24 Dec 2009 at 8:36
Issue 30 has been merged into this issue.
Original comment by Mohamma...@gmail.com
on 24 Dec 2009 at 8:38
Oh, I see. My problem (http://code.google.com/p/switchy/issues/detail?id=43) is
not
caused by Privoxy, but by my using dial-up connection. Sorry.
Original comment by xlu.2...@gmail.com
on 8 Jan 2010 at 12:01
@xlu.2007
No problem, I've closed the mentioned issue.
Thanks for your feedback.
Original comment by Mohamma...@gmail.com
on 8 Jan 2010 at 12:08
Fixed in v1.4.
Test the new version and tell me your opinions.
Original comment by Mohamma...@gmail.com
on 10 Jan 2010 at 4:17
Great, but still some problems:
1) it doesn't work if the name of the dial-up connection is Chinese.
2) I still can't get it to work with SOCKS 5 proxy. I don't know whether it's
the
SOCKS 5 support or the dial-up support problem.
Original comment by xlu.2...@gmail.com
on 11 Jan 2010 at 3:17
Attachments:
I checked the "enable switch rules" option and unchecked it. Now it works. I
don't
know why.
However, the speed is very very slow. If I use firefox with the same proxy, the
page
loads in about 1 second. Chrome takes more than 10 seconds. Is it because it
uses a
pac file to support Socks 5?
Original comment by xlu.2...@gmail.com
on 11 Jan 2010 at 3:56
@xlu.2007
(comment 7)
1) Please file this bug in a separate issue.
(comment 8)
I don't think so, because the PAC file is loaded only one time and then it's
cached by
browser.
Please test it again after you restart Chrome.
Original comment by Mohamma...@gmail.com
on 12 Jan 2010 at 10:56
@xlu.2007
(comment 7: 'it doesn't work if the name of the dial-up connection is Chinese')
Fixed in version 1.5.0
Original comment by Mohamma...@gmail.com
on 20 Jan 2010 at 10:53
@xlu.2007
i use version 1.6.0.1, but it still doesn't work if the name of the dial-up
connection is
Chinese.
The problom of 6.jpg is fixed, it can show the Chinese name in the screen, but
it goes
directly to the internet.
Original comment by gjcK...@gmail.com
on 15 Feb 2010 at 1:27
Original issue reported on code.google.com by
Gary.Hai
on 21 Dec 2009 at 5:42