According to https://www.torproject.org/docs/tor-manual.html.en Tor now supports
HTTPTunnelPort, i.e. serving as an incoming http proxy, if I understand that right.
HTTPTunnelPort [address:]port|auto [isolation flags]
Open this port to listen for proxy connections using the “HTTP CONNECT” protocol instead of SOCKS. Set this to 0 0 if you don’t want to allow “HTTP CONNECT” connections. Set the port to “auto” to have Tor pick a port for you. This directive can be specified multiple times to bind to multiple addresses/ports. See SOCKSPort for an explanation of isolation flags. (Default: 0)
In past we’ve run into a few issues where applications had http proxy support but not socks proxy support. In these cases one needed to involve privoxy or polipo as a http proxy to socks proxy translator, which is really cumbersome (and may not provide stream isolation if used more than one application using it at the same time).
Does anyone remember these use cases?
What new options will
HTTPTunnelPort give us at Whonix?