# Using Tor Browser's SOCKS Port

**URL:** https://forum.torproject.org/t/using-tor-browsers-socks-port/17718
**Category:** Core Tor
**Tags:** tor, tor-browser
**Created:** [March 4, 2025, 2:26am UTC](https://forum.torproject.org/t/using-tor-browsers-socks-port/17718 "2025-03-04T02:26:38Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Torceror](https://forum.torproject.org/user_avatar/forum.torproject.org/torceror/32/7336_2.png) [@Torceror](https://forum.torproject.org/u/Torceror)
#### Post date: [March 7, 2025, 2:58pm UTC](https://forum.torproject.org/t/using-tor-browsers-socks-port/17718/5 "2025-03-07T14:58:14Z")

</div>

Thank you @Protium_serratum for recommending HTTPTunnelPort.

For years I have used Polipo (deprecated) and currently Privoxy to provide an HTTP proxy pointing to Tor’s SOCKS5 port, and these worked well. Privoxy provides advanced filtering capabilities so I used that to create an additional whitelisting proxy server to keep an old Windows virtual machine in check.

I like the stream isolation advantage of HTTPTunnelPort, and I began testing HTTPTunnelPort with wget. I am using shell variables to only adjust the proxy for wget, but I noticed something unexpected.

HTTPTunnelPort appears to only work as an https\_proxy…not as an http\_proxy.

For example, this works as expected:  
export https\_proxy=“[http://127.0.0.1:9100/](http://127.0.0.1:9100/)” && wget (insert URL here)

For example, this does not work as expected:  
export http\_proxy=“[http://127.0.0.1:9100/](http://127.0.0.1:9100/)” && wget (insert URL here)

The version of wget I am using (1.21.2) does not support SOCKS5. I think that was a recent development.

I think the version of wget I am using either prefers an https\_proxy, does not work with http\_proxy, or HTTPTunnelPort provides https\_proxy.

Hopefully these notes will help @abc in troubleshooting.

---

_[View the full topic](https://forum.torproject.org/t/using-tor-browsers-socks-port/17718)._