[squid-users] ESI processor don't parse ESI content

Hi,
I would like to use Squid ESI processor on a reverse proxy.
I have compiled squid with --enable-esi.

Actually the website is ESI compliant because we have Akamai service on
it, and it's ok.

So i have setup my squid on the server with a minimal configuration, but
the esi in the page is not interpreted. It's a simple esi:include of a
html page.

Is there any tips to trigger the ESI processor? It's not automatic?

My small squid.conf:
acl manager proto cache_object
acl localhost src 127.0.0.1/32
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 443 # https
acl CONNECT method CONNECT
acl eurosport_websites dstdomain "/etc/squid3/squid_websites_domaines.conf"
http_access allow all
http_port 80 defaultsite=www.website.com vhost accel
cache_replacement_policy lru
cache_dir aufs /var/spool/squid3 5120 16 256
access_log /var/log/squid3/access.log squid
cache_log /var/log/squid3/cache.log
cache_store_log /var/log/squid3/store.log
minimum_expiry_time 0 seconds
cache_effective_user proxy
visible_hostname www.website.com
esi_parser libxml2
error_directory /usr/share/squid3/errors/French
always_direct allow website_websites
coredump_dir /var/spool/squid3

Thanks,
Damien Desmarets
Received on Fri Oct 03 2008 - 09:49:15 MDT