<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Google Chrome Socks Proxy Workaround</title> <atom:link href="http://geeklad.com/google-chrome-socks-proxy-workaround/feed" rel="self" type="application/rss+xml" /><link>http://geeklad.com/google-chrome-socks-proxy-workaround</link> <description></description> <lastBuildDate>Tue, 22 May 2012 02:33:00 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: tylerl</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-2062</link> <dc:creator>tylerl</dc:creator> <pubDate>Sat, 07 May 2011 23:09:00 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-2062</guid> <description> Chrome actually uses the Internet Explorer proxy settings. So if you set up a SOCKS proxy for IE, it will be used by chrome.</description> <content:encoded><![CDATA[<p>Chrome actually uses the Internet Explorer proxy settings. So if you set up a SOCKS proxy for IE, it will be used by chrome.</p> ]]></content:encoded> </item> <item><title>By: Kostya</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-1971</link> <dc:creator>Kostya</dc:creator> <pubDate>Thu, 27 Jan 2011 09:46:07 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-1971</guid> <description>Hello there.&lt;br&gt;To fix this problem for SOCKS5 (SSH-tunnel) in chrome:&lt;br&gt;1) add  --proxy-server=&quot;socks5://127.0.0.1:port&quot;, after chrome.exe&quot; in your shortcut;&lt;br&gt;2) switch off DNS prefetching function in options.&lt;br&gt;that&#039;s all.&lt;br&gt;Thanx to &lt;a href=&quot;http://habrahabr.ru/blogs/google_chrome/110587/&quot; rel=&quot;nofollow&quot;&gt;http://habrahabr.ru/blogs/goog...&lt;/a&gt;</description> <content:encoded><![CDATA[<p>Hello there.<br
/>To fix this problem for SOCKS5 (SSH-tunnel) in chrome:<br
/>1) add  &#8211;proxy-server=&#8221;socks5://127.0.0.1:port&#8221;, after chrome.exe&#8221; in your shortcut;<br
/>2) switch off DNS prefetching function in options.<br
/>that&#39;s all.<br
/>Thanx to <a
href="http://habrahabr.ru/blogs/google_chrome/110587/" rel="nofollow">http://habrahabr.ru/blogs/goog&#8230;</a></p> ]]></content:encoded> </item> <item><title>By: Kostya</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-1910</link> <dc:creator>Kostya</dc:creator> <pubDate>Thu, 27 Jan 2011 03:46:07 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-1910</guid> <description>Hello there.&lt;br&gt;To fix this problem for SOCKS5 (SSH-tunnel) in chrome:&lt;br&gt;1) add  --proxy-server=&quot;socks5://127.0.0.1:port&quot;, after chrome.exe&quot; in your shortcut;&lt;br&gt;2) switch off DNS prefetching function in options.&lt;br&gt;that&#039;s all.&lt;br&gt;Thanx to &lt;a href=&quot;http://habrahabr.ru/blogs/google_chrome/110587&quot; rel=&quot;nofollow&quot;&gt;http://habrahabr.ru/blogs/goog...&lt;/a&gt;/</description> <content:encoded><![CDATA[<p>Hello there.<br
/>To fix this problem for SOCKS5 (SSH-tunnel) in chrome:<br
/>1) add  &#8211;proxy-server=&#8221;socks5://127.0.0.1:port&#8221;, after chrome.exe&#8221; in your shortcut;<br
/>2) switch off DNS prefetching function in options.<br
/>that&#39;s all.<br
/>Thanx to <a
href="http://habrahabr.ru/blogs/google_chrome/110587" rel="nofollow">http://habrahabr.ru/blogs/goog&#8230;</a>/</p> ]]></content:encoded> </item> <item><title>By: gnug125</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-1698</link> <dc:creator>gnug125</dc:creator> <pubDate>Wed, 24 Mar 2010 14:00:12 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-1698</guid> <description>it would be much easier to simply append this to the end of your shortcut --proxy-server:socks5://localhost:3210</description> <content:encoded><![CDATA[<p>it would be much easier to simply append this to the end of your shortcut &#8211;proxy-server:socks5://localhost:3210</p> ]]></content:encoded> </item> <item><title>By: Kolomona</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-909</link> <dc:creator>Kolomona</dc:creator> <pubDate>Mon, 06 Apr 2009 19:59:39 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-909</guid> <description>Nice, I&#039;ll have to try it</description> <content:encoded><![CDATA[<p>Nice, I&#39;ll have to try it</p> ]]></content:encoded> </item> <item><title>By: proxy</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-884</link> <dc:creator>proxy</dc:creator> <pubDate>Thu, 26 Mar 2009 07:15:59 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-884</guid> <description>have you used TOR switching for firefox ? how good is your solutoin as compared to FF plugins ?</description> <content:encoded><![CDATA[<p>have you used TOR switching for firefox ? how good is your solutoin as compared to FF plugins ?</p> ]]></content:encoded> </item> <item><title>By: surfboards</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-854</link> <dc:creator>surfboards</dc:creator> <pubDate>Fri, 13 Mar 2009 07:31:14 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-854</guid> <description>Hey thanks a lot for such informative post, I was actually looking around for the same from a long time.</description> <content:encoded><![CDATA[<p>Hey thanks a lot for such informative post, I was actually looking around for the same from a long time.</p> ]]></content:encoded> </item> <item><title>By: Spike</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-834</link> <dc:creator>Spike</dc:creator> <pubDate>Tue, 03 Mar 2009 15:02:10 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-834</guid> <description>Looks like it&#039;s working!&lt;br&gt;Thanks!</description> <content:encoded><![CDATA[<p>Looks like it&#39;s working!<br
/>Thanks!</p> ]]></content:encoded> </item> <item><title>By: GeekLad</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-831</link> <dc:creator>GeekLad</dc:creator> <pubDate>Tue, 03 Mar 2009 03:04:24 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-831</guid> <description>All I have in my config is:&lt;br&gt;forward-socks4a / 127.0.0.1:1080 .&lt;br&gt;&lt;br&gt;and it works like a charm.  Try changing your lines to that and see if it&lt;br&gt;does the trick.</description> <content:encoded><![CDATA[<p>All I have in my config is:<br
/>forward-socks4a / 127.0.0.1:1080 .</p><p>and it works like a charm.  Try changing your lines to that and see if it<br
/>does the trick.</p> ]]></content:encoded> </item> <item><title>By: Spike</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-828</link> <dc:creator>Spike</dc:creator> <pubDate>Sat, 28 Feb 2009 18:53:06 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-828</guid> <description>Hmm, I currently enable an SSH tunnel session with one of my offsite boxes. And then use Firefox to route through localhost:1080.&lt;br&gt;&lt;br&gt;Yesterday I installed Privoxy for Chrome and tried it, and it immediately showed my SSH box&#039;s IP during surfing. I tried it today, and it doesn&#039;t work. So, I did the main configuration file (I hadn&#039;t earlier) and added:&lt;br&gt;&lt;br&gt;forward   /      localhost:1080&lt;br&gt;forward   :443   .&lt;br&gt;&lt;br&gt;And now I get this on chrome when I go to whatismyip.com:&lt;br&gt;Empty server or forwarder response.&lt;br&gt;The connection has been closed but Privoxy didn&#039;t receive any data.&lt;br&gt;&lt;br&gt;I&#039;m stumped.</description> <content:encoded><![CDATA[<p>Hmm, I currently enable an SSH tunnel session with one of my offsite boxes. And then use Firefox to route through localhost:1080.</p><p>Yesterday I installed Privoxy for Chrome and tried it, and it immediately showed my SSH box&#39;s IP during surfing. I tried it today, and it doesn&#39;t work. So, I did the main configuration file (I hadn&#39;t earlier) and added:</p><p>forward   /      localhost:1080<br
/>forward   :443   .</p><p>And now I get this on chrome when I go to whatismyip.com:<br
/>Empty server or forwarder response.<br
/>The connection has been closed but Privoxy didn&#39;t receive any data.</p><p>I&#39;m stumped.</p> ]]></content:encoded> </item> <item><title>By: GeekLad</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-813</link> <dc:creator>GeekLad</dc:creator> <pubDate>Sun, 22 Feb 2009 18:02:08 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-813</guid> <description>Actually, Google dropped the beta designation from&lt;br&gt;Chrome&lt;http://geeklad.com/google-chrome-20&gt;a couple of months ago.&lt;br&gt;However, if you ask me I&#039;d say yeah, it&#039;s still&lt;br&gt;more like a beta browser.  If the browser is still having to make use of&lt;br&gt;Internet Explorer components and does not have a standalone engine for&lt;br&gt;handling proxies, I&#039;d still call it a beta.&lt;br&gt;I suspect that once the Mac OS X and Linux versions come along, it should&lt;br&gt;finally be handling proxy support within the app, and this workaround will&lt;br&gt;no longer be needed.  It does take some work, but if you are intent on using&lt;br&gt;Chrome behind a socks firewall, it is probably one of the few viable&lt;br&gt;solutions out there.</description> <content:encoded><![CDATA[<p>Actually, Google dropped the beta designation from<br
/>Chrome&lt;<a
href="http://geeklad.com/google-chrome-20&gt;a" rel="nofollow">http://geeklad.com/google-chrome-20&gt;a</a> couple of months ago.<br
/>However, if you ask me I&#39;d say yeah, it&#39;s still<br
/>more like a beta browser.  If the browser is still having to make use of<br
/>Internet Explorer components and does not have a standalone engine for<br
/>handling proxies, I&#39;d still call it a beta.<br
/>I suspect that once the Mac OS X and Linux versions come along, it should<br
/>finally be handling proxy support within the app, and this workaround will<br
/>no longer be needed.  It does take some work, but if you are intent on using<br
/>Chrome behind a socks firewall, it is probably one of the few viable<br
/>solutions out there.</p> ]]></content:encoded> </item> <item><title>By: proxie</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-812</link> <dc:creator>proxie</dc:creator> <pubDate>Sun, 22 Feb 2009 17:52:25 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-812</guid> <description>Is that not a bit much work for chrome its still beta...</description> <content:encoded><![CDATA[<p>Is that not a bit much work for chrome its still beta&#8230;</p> ]]></content:encoded> </item> <item><title>By: buddhakwee</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-794</link> <dc:creator>buddhakwee</dc:creator> <pubDate>Fri, 13 Feb 2009 13:07:28 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-794</guid> <description>I want to get backlink for my site &lt;a href=&quot;http://hi-rank.com&quot; rel=&quot;nofollow&quot;&gt; hi-rank&lt;/a&gt; THankyou</description> <content:encoded><![CDATA[<p>I want to get backlink for my site <a
href="http://hi-rank.com" rel="nofollow"> hi-rank</a> THankyou</p> ]]></content:encoded> </item> <item><title>By: PageRank 0 to 3 in Less than a Month</title><link>http://geeklad.com/google-chrome-socks-proxy-workaround/comment-page-1#comment-24</link> <dc:creator>PageRank 0 to 3 in Less than a Month</dc:creator> <pubDate>Sun, 28 Sep 2008 04:46:09 +0000</pubDate> <guid
isPermaLink="false">http://geeklad.com/?p=296#comment-24</guid> <description>[...] problems with running Google Chrome behind a SOCKS proxy.  That led me to come up with my own workaround for getting Google Chrome to work with a SOCKS proxy.  Currently, if you search on Google for google chrome socks, my article appears on the first page [...]</description> <content:encoded><![CDATA[<p>[...] problems with running Google Chrome behind a SOCKS proxy.  That led me to come up with my own workaround for getting Google Chrome to work with a SOCKS proxy.  Currently, if you search on Google for google chrome socks, my article appears on the first page [...]</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 26/46 queries in 0.009 seconds using disk: basic
Object Caching 447/448 objects using disk: basic

Served from: geeklad.com @ 2012-05-23 19:51:28 -->
