Re: [squid-users] issue with htcp support on squid

Thank you for your help, Chris.

I turned on all the debug_options you suggested and found out the
problem. By mistake I disabled
icp_port to use htcp. The log file indicated that no ICP socket. The
problem is solved now.

On Tue, Dec 9, 2008 at 11:23 AM, Chris Robertson <crobertson_at_gci.net> wrote:
> Bostonian wrote:
>>
>> While I am trying HTCP support for squid 3.0 stable 10, I ran into
>> some issues. Hope someone could give me some leads on how to solve it.
>>
>> Here is my setting. I have two Linux running squid, which is compiled
>> with --enable-htcp. One is used as parent for the other.
>>
>> On the parent side (188.168.75.20). I put the following configs:
>>
>> localnet 188.168.0.0/16
>>
>> htcp_port 4827
>> htcp_access allow localnet
>> htcp_access deny all
>>
>> On the child side (188.168.77.20), I put the following configs:
>>
>> localcnet 188.168.0.0/16
>>
>
> Perhaps a typo?
>
>> htcp_port 4827
>> htcp_access allow localnet
>> htcp_access deny all
>>
>> cache_peer 188.168.75.20 3128 4827 htcp
>>
>
> Should this not be "cache_peer parent 188.168.75.20 3128 4827 htcp"? Again,
> this could just be a typo in your email.
>
> As a side note, listening for htcp queries on the child proxy is unnecessary
> in this case.
>
>> However, whenever I am trying to access any website that is not in the
>> cache of the child, curl returns the following error code:
>>
>> curl: (52) Empty reply from server
>>
>> I hope that I explained it clearly enough. Any suggestioin is highly
>> appreciated
>>
>
> Check the cache.log for any errors. If you don't see anything regarding
> peer selection, upping debugging on section 44 and section 31 (debug_options
> 44,9 31,9 ALL,1) should help.
>
> Chris
>
Received on Tue Dec 09 2008 - 21:19:21 MST