Re: [squid-users] Content Encoding Error

On 11/05/2013 12:58 a.m., CACook_at_quantum-sci.com wrote:
> On Thursday, May 09, 2013 09:18:53 PM Amos Jeffries wrote:
>> On 10/05/2013 2:24 a.m., CACook_at_quantum-sci.com wrote:
>>> OK I guess I have to ditch Squid. I can't live with this.
>>>
>> Well, if you cant or dont want to supply the information needed to help
>> there is very little help possible.
> LOL, it appears you feel I am being uncooperative.
>
>
>>>>> What does your squid.conf contain?
>>>> http://pastebin.com/ke5WQkdj
>> This is the squid.conf documentation with some lines uncommented.
>> Notably the _incomplete example_ of how to do anonymous proxy
>> configuration for HTTP/1.0 traffic. Few of the HTTP/1.1 headers are
>> handled there.
>>
>> The error you report is usually seen when Accept*, Content-Encoding or
>> Tansfer-Encoding are screwed with. The logs you wont supply would have
>> shown which was the problem.
> 'The logs I -won't- supply'? You mean the logs I -can't- supply because Squid hasn't made logs for me for months.

cant or wont. I wasn't sure. Not everyone using those anonymous configs
are willing to post the details here in public.

If you like we'd probably get that sorted. I'm thinking its a
permissions issue in the logs directory, overflowing logs due to log
rotation errors (ALL,3 can output a lot of data and get into a bit of
trouble getting past 2 or 4 GB).

> The squid.conf documentation? That is exactly what comes with Debian's squid package. What do you mean documentation? Where is the secret place that you are getting the real .conf file?

With the squid3 packages you will find it in /etc/squid3/squid.conf.
With the file you posted at squid.conf.documented.
if you are building your own and installign over an existing Squid, you
will find the new default config in squid.conf.default next to your
squid.conf and an updated documentation file at squid.conf.documented.

> "_incomplete example_ "? Where is the secret place that you get the full header anonymization?

There isn't one published that I'm aware of. Its just that nobody has
updated that one in most of a decade to allow the more recently created
required headers through. Like you are probably encountering errors due
to Transfer-Encoding and TE being missing.

Amos
Received on Fri May 10 2013 - 13:17:23 MDT