Quoting Henrik Nordstrom [EMAIL PROTECTED]:
A workaround is to forward CONNECT requests over http as usual instead
of wrapping them in yet another ssl layer. Another workaround if you
really MUST wrap the CONNECT requests in SSL between the proxy servers
is to offload the SSL wrapper from Squid
Quoting Amos Jeffries [EMAIL PROTECTED]:
in access.log
192.168.0.1 TCP_MISS/000 0 CONNECT sourceforge.net:443 -
FIRST_UP_PARENT/__ip__ -
What does cache.log have to say about those failed requests?
What version is the parent cache? Same details from them if possible.
it says nothing
On tor, 2008-05-15 at 11:27 +0300, Jancs wrote:
2008/05/15 11:20:04| clientNegotiateSSL: Error negotiating SSL
connection on FD 17: error:1407609B:SSL
routines:SSL23_GET_CLIENT_HELLO:https proxy request (1/-1)
This means a proxy client contacted a https_port when it should have
talked to
Quoting Henrik Nordstrom [EMAIL PROTECTED]:
On tor, 2008-05-15 at 11:27 +0300, Jancs wrote:
2008/05/15 11:20:04| clientNegotiateSSL: Error negotiating SSL
connection on FD 17: error:1407609B:SSL
routines:SSL23_GET_CLIENT_HELLO:https proxy request (1/-1)
This means a proxy client contacted a
On tor, 2008-05-15 at 19:16 +0300, Jancs wrote:
didn't got:
i am on my machine trying to contact https://sourceforge.net/my/, my
browser contacts slave cache, which in it's order connects to parent
cache using ssl and parent is supposed to connect to the site I want.
In no place use
Quoting Chris Robertson [EMAIL PROTECTED]:
So the child Squid is trying to negotiate an SSL connection with a port
on the Parent that's not set up to accept it. See
http://www.squid-cache.org/Versions/v3/3.0/cfgman/https_port.html for
the proper directive to terminate an SSL connection.
I
Janis wrote:
Quoting Chris Robertson [EMAIL PROTECTED]:
So the child Squid is trying to negotiate an SSL connection with a port
on the Parent that's not set up to accept it. See
http://www.squid-cache.org/Versions/v3/3.0/cfgman/https_port.html for
the proper directive to terminate an SSL
Quoting Amos Jeffries [EMAIL PROTECTED]:
Janis wrote:
I succeded in setting up chain of proxies using ssl for
inter-communication, but - i lost possibility to tunnel https
requests - instead of it i get empty page without any messages.
Where should I look to correct this?
Could be
Jancs wrote:
Quoting Amos Jeffries [EMAIL PROTECTED]:
Janis wrote:
I succeded in setting up chain of proxies using ssl for
inter-communication, but - i lost possibility to tunnel https
requests - instead of it i get empty page without any messages.
Where should I look to correct this?
On tor, 2008-05-08 at 14:42 +0300, Janis wrote:
I succeded in setting up chain of proxies using ssl for
inter-communication, but - i lost possibility to tunnel https requests
- instead of it i get empty page without any messages.
Hmm.. I think there is an open bug report for this.
Janis wrote:
Quoting Chris Robertson [EMAIL PROTECTED]:
So the child Squid is trying to negotiate an SSL connection with a port
on the Parent that's not set up to accept it. See
http://www.squid-cache.org/Versions/v3/3.0/cfgman/https_port.html for
the proper directive to terminate an SSL
Quoting Chris Robertson [EMAIL PROTECTED]:
On the parent server is acl allowing this secondary server to connect.
Are you using an http_port, or an https_port directive on the parent
server? What does it look like?
it looks so:
http_port IP:port
Janis
Janis wrote:
Quoting Chris Robertson [EMAIL PROTECTED]:
On the parent server is acl allowing this secondary server to connect.
Are you using an http_port, or an https_port directive on the parent
server? What does it look like?
it looks so:
http_port IP:port
Janis
So the child Squid
Quoting Chris Robertson [EMAIL PROTECTED]:
So the child Squid is trying to negotiate an SSL connection with a port
on the Parent that's not set up to accept it. See
http://www.squid-cache.org/Versions/v3/3.0/cfgman/https_port.html for
the proper directive to terminate an SSL connection.
so,
Hi!
I tried to configure secondary proxy to use ssl for communications
with parent proxy, but can not succed.
there are cnf lines od secondary server:
cache_peer IP_addr parent PORT 3130 proxy-only ssl \
sslcert=/etc/ssl/host.cert \
sslkey=/etc/ssl/host.key \
sslflags=DONT_VERIFY_PEER
(I
Janis wrote:
Hi!
I tried to configure secondary proxy to use ssl for communications
with parent proxy, but can not succed.
there are cnf lines od secondary server:
cache_peer IP_addr parent PORT 3130 proxy-only ssl \
sslcert=/etc/ssl/host.cert \
sslkey=/etc/ssl/host.key \
16 matches
Mail list logo
