Thanks Henrik ... It work, somehow in the testing those PHP files got onto the cache ...
Now I investigating about no_cache ACL .... In my very quickly small research does this lines will do the trick for PHP files
acl DENYPHPS urlpath_regex php no_cache deny DENYPHPS
I am not very familiar with regexp syntax, I will research more But in this case this rule I think is not very effective ... Because www.php.net will pass (no cache) and that is not the idea Is there somo useful links for a tutorial about regexp syntax ...
Thanks
Henrik Nordstrom wrote:
On Tue, 16 Dec 2003, Rogger Vasquez wrote:
But others execute with no problem ... and they are in the same directory, first I thougth that I had
the PHP engine OFF in that directory, but was not the case ,,,
When I check the access.log in the squid, I notice that the ones executing correctly had TCP_MISS ...
And the others TCP_MEM_HIT ...
Ok. So somehow these has entered your cache. If the cached data is the PHP
script then your new server did have the PHP engine OFF for a while
causing the pages to get cached (there is no way the PHP script as such could have left the origin server otherwise)
To correct this you can either
a) PURGE the offending objects when identified
b) Use the no_cache ACL to deny use of the cache for the pages
c) Clean your cache.
Regards Henrik
