Re: Connecting to special ports through Tor/Privoxy

2006-11-03 Thread Fabian Keil
[EMAIL PROTECTED] wrote:

> >> When I want to connect through Tor to special port as 8443 by https
> >> (Plesk panels), I simply cannot and always get a blank page. (Usual
> >> config for https is 127.0.0.1:8118)
> 
> > Some Privoxy configurations limit CONNECT to port 443
> > or block it all together. By default Privoxy answers those
> > request with an error message inside the HTTP headers because
> > some user agents get confused otherwise. If you use a browser
> > that hides HTTP headers, these error messages are obviously
> > easy to overlook.

> The problem isn't on the port 443, but 8443.

As I already wrote above, CONNECT requests are limited to
port 443 (or blocked to every port) by default and as a result
attempts to CONNECT to port 8443 get blocked.
 
> The Plesk addresses are https://domain/etc:8443

Which means the proxy-using browser will use HTTP CONNECT while
trying to open the SSL connection.
 
> Usual addresses https work fine with my config, it is when I want to
> connect to the port 8443 that it fails.

Usually HTTPS connections use port 443 which isn't blocked.

> And I have no Privoxy error page, nothing. Just a blank page.

As mentioned above, the error message is send as HTTP header.

Fabian
-- 
http://www.fabiankeil.de/


signature.asc
Description: PGP signature


Re: Connecting to special ports through Tor/Privoxy

2006-11-03 Thread Dave Page
On Fri, Nov 03, 2006 at 07:58:43AM -0500, [EMAIL PROTECTED] wrote:
> 
> > Some Privoxy configurations limit CONNECT to port 443
> > or block it all together. By default Privoxy answers those
> > request with an error message inside the HTTP headers because
> > some user agents get confused otherwise. If you use a browser
> > that hides HTTP headers, these error messages are obviously
> > easy to overlook.

> The problem isn't on the port 443, but 8443.

> The Plesk addresses are https://domain/etc:8443

> Usual addresses https work fine with my config, it is when I want to
> connect to the port 8443 that it fails. And I have no Privoxy error
> page, nothing. Just a blank page.

This is because your Privoxy is configured by default to only allow
HTTPS connections to port 443, as the original response to your question
stated. You need to configure Privoxy to enable HTTPS connections to
other ports.

This is a Frequently Asked Question - see
http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#head-b53af6f5168ddc7ddbed28ec8a62381d56d02ffb
for the solution.

Dave
-- 
Dave Page <[EMAIL PROTECTED]>
Jabber: [EMAIL PROTECTED]


Re: Connecting to special ports through Tor/Privoxy

2006-11-03 Thread force44
>> When I want to connect through Tor to special port as 8443 by https
>> (Plesk panels), I simply cannot and always get a blank page. (Usual
>> config for https is 127.0.0.1:8118)

> Some Privoxy configurations limit CONNECT to port 443
> or block it all together. By default Privoxy answers those
> request with an error message inside the HTTP headers because
> some user agents get confused otherwise. If you use a browser
> that hides HTTP headers, these error messages are obviously
> easy to overlook.



The problem isn't on the port 443, but 8443.

The Plesk addresses are https://domain/etc:8443

Usual addresses https work fine with my config, it is when I want to connect to 
the port 8443 that it fails. And I have no Privoxy error page, nothing. Just a 
blank page.


F44


Re: Connecting to special ports through Tor/Privoxy

2006-11-03 Thread Fabian Keil
[EMAIL PROTECTED] wrote:

> Config: Firefox 2 Privoxy Tor (Vidalia)
> 
> 
> When I want to connect through Tor to special port as 8443 by https
> (Plesk panels), I simply cannot and always get a blank page. (Usual
> config for https is 127.0.0.1:8118)

Some Privoxy configurations limit CONNECT to port 443
or block it all together. By default Privoxy answers those
request with an error message inside the HTTP headers because
some user agents get confused otherwise. If you use a browser
that hides HTTP headers, these error messages are obviously
easy to overlook.

> To solve the problem, I have to delete all entries the https entry, and
> so I use the Socks5 proxy on 127.0.0.1:9050

> Isn't there a way (probably something to add in the Privoxy config?) to
> be able to connect through Tor to https://x:8443 without using the
> Socks5 proxy?

You can just make an exception or disable limit-connect for all sites:
http://www.privoxy.org/user-manual/actions-file.html#LIMIT-CONNECT

If you use Privoxy 3.0.5 beta you could also enable:
http://www.privoxy.org/user-manual/actions-file.html#TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS
to get the standard HTML error message for blocked sites next time
you try to CONNECT to a blocked port. Please read the fine print
about its limitations first.

Fabian
-- 
http://www.fabiankeil.de/


signature.asc
Description: PGP signature


Connecting to special ports through Tor/Privoxy

2006-11-02 Thread force44
Hello!

Not sure it is the best place here for this topic, sorry if I mistake!

Config: Firefox 2 Privoxy Tor (Vidalia)


When I want to connect through Tor to special port as 8443 by https (Plesk 
panels), I simply cannot and always get a blank page. (Usual config for https 
is 127.0.0.1:8118)

To solve the problem, I have to delete all entries the https entry, and so I 
use the Socks5 proxy on 127.0.0.1:9050

Earlier I used the multiproxy extension for Firefox, had one entry "tor 
(usual)" and one entry "Tor (Socks5)". So that was easy to change.

Using now TorButton, this isn't the same, as I have to edit the "Preferences" 
every time.

Isn't there a way (probably something to add in the Privoxy config?) to be able 
to connect through Tor to https://x:8443 without using the Socks5 proxy?

Thank you