Fwd: Re: [squid-users] Squid Re-cache problem

Amos,

I was reading your email again and saw this part at the end:
"
> Amos
> --
> I'm in Sydney for a few days now:
>
> Please use Squid 2.7.STABLE3 or 3.0.STABLE8
>
"

That means, we should use one of those versions of SQUID?
Did you saw the configuration I send you?

Regards
Ana Leal

----- Mensaje reenviado de aleal_at_remsolu.com -----
   Fecha: Mon, 18 Aug 2008 08:27:33 +0200
      De: Ana Leal <aleal_at_remsolu.com>
Responder-A: Ana Leal <aleal_at_remsolu.com>
 Asunto: Re: [squid-users] Squid Re-cache problem
    Para: Amos Jeffries <squid3_at_treenet.co.nz>

Hi Amos,

The Proxy Verson is: 2.4.STABLE6
The Proxy Configuration is:
http_port $LNXIP:9080
visible_hostname lnx$OFCOME
error_directory /usr/lib/squid/errors/Spanish cache_mgr Centro_Soporte
hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \? \.asp$ no_cache deny QUERY cache_access_log
/var/log/squid/access.log cache_store_log none request_body_max_size 8 MB acl
alldst dst 0.0.0.0/0.0.0.0 acl all src 0.0.0.0/0.0.0.0 acl $OFCOME src $LNXNET
acl cisicret src 10.5.4.0/255.255.254.0 acl manager proto cache_object acl
localhost src 127.0.0.1/255.255.255.255 acl SSL_ports port 443 563 444
acl SSL_ports port 448 # U. Rioja ademas del 82 usa el 448
acl SSL_ports port 8443 # Acceso zona segura a 060.es
acl Safe_ports port 80-83 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 563 444 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl Safe_ports port 901 # SWAT
acl Safe_ports port 448 # U. Rioja ademas del 82 usa el 448
acl Safe_ports port 8443
$SQD_ACL1
$SQD_ACL2
acl purge method PURGE
acl CONNECT method CONNECT
acl wwwicex dstdomain www.icex.es
acl portalcma dstdomain portal.icex.es cdc.portal.icex.es cache_peer 10.5.5.18
parent 9080 0 no-query no-digest no-netdb-exchange acl badex dstdomain
"/etc/squid/badex.acl"
acl badexip dst "/etc/squid/badexip.acl"
no_cache deny badex
no_cache deny badexip
no_cache deny wwwicex
cache_peer_access 10.5.5.18 allow badex
cache_peer_access 10.5.5.18 allow badexip cache_peer_access 10.5.5.18 allow
badex CONNECT cache_peer_access 10.5.5.18 allow badexip CONNECT
cache_peer_access 10.5.5.18 allow wwwicex cache_peer_access 10.5.5.18 allow
portalcma http_access allow manager localhost http_access deny manager
http_access allow purge localhost http_access deny purge http_access deny
!Safe_ports http_access deny CONNECT !SSL_ports http_access allow localhost
http_access allow $OFCOME http_access deny all icp_access allow all
append_domain .icex.es never_direct allow badex never_direct allow badexip
never_direct allow portalcma never_direct deny alldst

There's anything wrong or missing whith this configuration?

Do you think that using the Squid 2.7.STABLE3 or 3.0.STABLE8 will resolve the
case? If so, there's anything to pay attention for when configuring it?

Regards
Ana Leal

Quoting Amos Jeffries <squid3_at_treenet.co.nz>:

> Ana Leal wrote:
>> Hi everyone!
>>
>> I?m having a problem with the cash of an application I use (ITSM from BMC)
>> with Internet Explorer 6.0.
>>
>> The normal architecture for this application to work is: Internet
>> client 6.0 à
>> Squid Proxy à Mid-tier (BMC) à Application (ITSM BMC).
>>
>> But when the proxy is connected, this application doesn?t work as expect.
>>
>> I had prove that if I ?oblige? the system to ?re-cache? the web every
>> time is accessed (configuring the Internet Explorer to check new
>> changes every
>> time a page is visited)
>
> understood.
>
>> and not allowing the access trough the Proxy to the
>> Mid-tier that supports the application
>
> huh! how? and what is the proxy config
>
>> (since it doesn?t have the cache of
>> the proxy it has to re-cache every time) it works perfectly!
>
> Sounds like:
> a) you are playing with refresh_pattern to ignore the application
> required Cache-Controls.
> b) the application is broken its own cache-controls.
>
>> But this situation creates a problem to the web users:
>>
>> This RE-CACHE, provokes a very slow internet performance since the
>> cache has to
>> be done every time the page is open.
>>
>> Does anyone have/had a similar problem? How did you resolve it? It?s a Squid
>> Proxy bug? It could be a version problem?
>>
>> Can anyone help me on this issue, please?
>>
>> Thanks
>>
>> Ana Leal
>>
>
> Amos
> --
> I'm in Sydney for a few days now:
>
> Please use Squid 2.7.STABLE3 or 3.0.STABLE8
>
Received on Wed Aug 20 2008 - 10:10:29 MDT