On lör, 2008-06-07 at 09:58 +0800, Ken W. wrote:
2008/6/7 Henrik Nordstrom [EMAIL PROTECTED]:
But you are quite likely to run into issues with the server sending out
http:// URLs in it's responses unless the server has support for running
behind an SSL frontend. See for example the
2008/6/7 Henrik Nordstrom [EMAIL PROTECTED]:
Thanks Henrik.
Under my setting, can squid work correctly for this flow?
clients --https-- squid --http-- webserver
webserver --http-- squid --https-- clients
Again, yes, provided your web server application has support for being
used
Hello members,
My squid's config for https looks as below:
http_port 80 accel vhost
https_port 443 accel vhost cert=/usr/local/squid/etc/ssl/server.cert
key=/usr/local/squid/etc/ssl/server.key
cache_peer 12.34.56.78 parent 80 0 no-query front-end-https=auto
originserver name=origin_1
acl
On lör, 2008-06-07 at 18:29 +0800, Ken W. wrote:
2008/06/07 14:37:02| httpsAccept: Error allocating handle:
error:0906A068:PEM routines:PEM_do_header:bad password read
Your SSL key is encrypted and you have not given the encryption key to
Squid so it can not set up the SSL proper.
Decrypt the
( I'm sorry that this was my third message for the same question to the list.
b/c the before two messages sent from yahoo got lost...)
Hello members,
I want to set squid, which accepts https from clients, then forward the
request to original server with http protocal.
This is the setting I
On fre, 2008-06-06 at 22:59 +0800, Ken W. wrote:
I want to set squid, which accepts https from clients, then forward the
request to original server with http protocal.
This is the setting I considered:
https_port 443 accel vhost cert=/squid/etc/xxx.crt key=/squid/etc/xxx.key
Hello members,
I want to set squid, which accepts https from clients, then forward the
request to original server with http protocal.
This is the setting I considered:
https_port 443 accel vhost cert=/squid/etc/xxx.crt key=/squid/etc/xxx.key
protocol=http
cache_peer 10.0.0.1 parent 80 0
2008/6/7 Henrik Nordstrom [EMAIL PROTECTED]:
But you are quite likely to run into issues with the server sending out
http:// URLs in it's responses unless the server has support for running
behind an SSL frontend. See for example the front-end-https cache_peer
option.
Thanks Henrik.
Under
.
-Original Message-
From: Loc Nguyen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 27, 2004 3:23 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [squid-users] HTTPS questions
Hi everyone,
I have few questions, I hope that you can help:
I want to setup a HTTPS accelerator
: [squid-users] HTTPS questions
===8==Original message text===
On Tue, 27 Jan 2004, Derek Winkler wrote:
cache_peer owahost.algorithmics.com parent 443 0 no-query ssl proxy-only
originserver login=PASS sslcert=/opt/squid/etc/owahost.algorithmics.com.crt
sslkey=/opt/squid
: [squid-users] HTTPS questions
===8==Original message text===
On Tue, 27 Jan 2004, Loc Nguyen wrote:
I have few questions, I hope that you can help:
I want to setup a HTTPS accelerator using squid. The
environment is:
Client - HTTPS - Squid accelerator - HTTPS
i've asked to be removed countless times. here's another message that
i didn't want. it's really not that hard to remove somebody is it...
This is a forwarded message
From: Loc Nguyen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Tuesday, January 27, 2004, 3:23:14 PM
Subject: [squid-users] HTTPS
On Tue, 27 Jan 2004, Loc Nguyen wrote:
I have few questions, I hope that you can help:
I want to setup a HTTPS accelerator using squid. The
environment is:
Client - HTTPS - Squid accelerator - HTTPS
webserver
Then you need Squid-3, or alternatively Squid-2.5 + SSL update patch from
On Tue, 27 Jan 2004, Derek Winkler wrote:
cache_peer owahost.algorithmics.com parent 443 0 no-query ssl proxy-only
originserver login=PASS sslcert=/opt/squid/etc/owahost.algorithmics.com.crt
sslkey=/opt/squid/etc/owahost.algorithmics.com.key sslflags=DONT_VERIFY_PEER
You don't need the
14 matches
Mail list logo
