[squid-users] no front-end-https option after compiling squid-3.0.PRE3

From: Martin Burke <[email protected]>
Date: Wed, 16 Mar 2005 19:23:23 -0500

I'm trying to compile a version of squid with the front-end-https
option in order to reverse-proxy for our Exchange 2003 OWA server.
The squid server is a Gentoo Linux box, so the newest package
available through emerge is 2.5.9-r1 which doesn't recognize
front-end-https.

After compiling squid-3.0.PRE3 with ./configure --enable-ssl, I get
the following error with squid -k parse:

2005/03/16 19:06:41| parseConfigFile: 'squid.conf' line 5
unrecognized: 'front-end-https=auto'

Below is the config file I'm using, cobbled together from Henrik
Nordstrom's suggested config file and one that works when
reverse-proxying for our old Exchange 5.5 OWA server:

Thanks for any assistance.

Martin Burke
National Center for Missing & Exploited Children
703-837-6436 office
571-259-1731 cell
mburke@ncmec.org

--------
visible_hostname testmail.ncmec.org
https_port 443 defaultsite=testmail.ncmec.org
cert=/etc/squid/webmail.crt key=/etc/squid/webmail.key

cache_peer 172.25.4.51 parent 80 0 no-query originserver front-end-https=auto

hosts_file /etc/squid/hosts

cache_mgr helpdesk@ncmec.org
cache_effective_user squid
cache_effective_group squid

http_port 127.0.0.1:8080

emulate_httpd_log on

acl acl_testmail dstdomain testmail.ncmec.org

http_access allow acl_testmail

acl to_index urlpath_regex /$
acl to_favicon urlpath_regex /favicon.ico$ acl to_exchange
urlpath_regex /exchange http_access allow to_index http_access allow
to_favicon http_access allow to_exchange

acl all src 0.0.0.0/0.0.0.0
http_access deny all
------------
Received on Wed Mar 16 2005 - 17:23:26 MST

This archive was generated by hypermail pre-2.1.9 : Fri Apr 01 2005 - 12:00:02 MST