Re: [squid-users] Unparsable headers? Squid as reverse-proxy.

Squid strips query terms by default in the logs. This can be disabled
and the full URL will be logged....stripping or not stripping the query
terms has no bearing on cacheability (though some of your acls /are/
preventing caching of URLs with query terms).

To get logging of those terms:

strip_query_terms off

To make those objects potentially cacheable (other tweaks to your origin
may be required), get rid of these two lines in your squid.conf:

acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY

BTW-My Virtual Model is /way/ cool. My girlfriend used it last week at
the Land's End site, and it was quite nifty.

David Robillard wrote:
> Hello squid-users,
>
> I am trying to setup squid as a reverse-proxy for an application
> called compositor which was developped in-house as an apache module.
> Compositor generates and sends images to client web browsers.
>
> The idea is to cache the images in order to lower to load on the
> compositor server.
>
> I have successfully configured squid as a reverse-proxy for static images.
> But unfortunately, I can't seem to make it happen for the compositor server.
>
>>From the store.log file, it seems that squid is unable to parse the HTTP
> headers sent from the compositor-server. Why is that? Could this prevent
> the image to be cached to disk?
>
> If someone could help me in this issue, it would be really appreciated.

-- 
Joe Cooper <joe@swelltech.com>
http://www.swelltech.com
Web Caching Appliances and Support