Re: [squid-users] TCP_MISS:DIRECT problems with http_accel configuration and cache (help please)

I've just been instructed to "get this working with 2.5 first" ;-)

I did try these mods and still get TCP_MISS

It's worth noting that for experimental purposes, the web server AND
squid daemon live on the same machine - though I'm using different
ports, so thought that's not optimal (or even secure, perhaps) it should
still work.

_F

Pablo Garc�a wrote:
> The Accel configuration for 2.6 changes.
> Basically you have to define the servers, url, domains, etc you're
> going to accelerate in the configuration using a combination of
> cache_peer + acl + cache_peer_access + never_direct
> Ej : you have to accelerate www.example.com that resides on 10.1.1.1,
> then your config should be like this
>
> http_port 80 defaultsite= www.example.com vhost
> cache_peer 10.1.1.1 parent 80 0 no-query originserver
> acl accel_host dstdomain .example.com
> cache_peer_access 10.1.1.1 allow accel_host
>
> acl all src 0.0.0.0/0.0.0.0
> never_direct deny all
>
> Regards, Pablo
>
>
> On 10/13/06, Pablo Garc�a <malevo@gmail.com> wrote:
>> Forrester, would you provide an example of an object not being cached ?
>>
>>
>>
>> On 10/13/06, Forrest Aldrich <forrie@forrie.com> wrote:
>> >
>> >
>> > Benno Blumenthal wrote:
>> > > You have a line
>> > >
>> > >
>> > > no_cache deny QUERY
>> > >
>> > >
>> > > I believe that implies the next line is
>> > >
>> > > no_cache allow all
>>
Received on Fri Oct 13 2006 - 12:13:27 MDT