Re: [squid-users] httpd_accel

this way it cannot work. best way maybe to use squid as ssl-gateway on port
443:
than the connection between squid-client is encrypted, between squid-server
not:

use squid 2.5S1, compile it with ssl-support.
http_port 80 (if you need it)
https_port 443 cert=your_cert key=your_key

to have both ways encrypted, you can only use the connect-method, but its
probably not what you want, cause the clienst must be configured to use
squid as https-proxy.

alp

----- Original Message -----
From: <RKRAWCZYK@fmlogistic.pl>
To: <squid-users@squid-cache.org>
Sent: Friday, October 18, 2002 11:43 AM
Subject: [squid-users] httpd_accel

> Hi
>
> Does it is possible ?
>
> 192.168.1.14 (https server, port 443)
> |
> |
> Squid (213.240.x.x) (+httpd_accel)
> |
> |
> Internet
>
> If I use standard configuration (like below) :
>
> http_port 80
> httpd_accel_host 192.168.1.14
> httpd_accel_port 443
> httpd_accel_single_host on
>
> I get error message (from 192.168.1.14):
>
> Bad Request
> Your browser sent a request that this server could not understand.
> Reason: You're speaking plain HTTP to an SSL-enabled server port.
> Instead use the HTTPS scheme to access this URL, please.
>
>
> Thanks for help
>
> Robert
>
> -------------------------------------------------
> Robert Krawczyk
> FM Logistic IT CE
> rkrawczyk@fmlogistic.pl
> -------------------------------------------------
>
Received on Fri Oct 18 2002 - 06:41:13 MDT