No -- from the origin. My real question is, are you sure that url is set to be
cacheable?
On Friday, January 29, 2016 9:53 AM, Muhammad Faisal <[email protected]>
wrote:
Header from client side? I have ignore client side no_cache while server side
no_cache will be effective.
On 1/29/2016 10:22 PM, Miles Libbey wrote:
Can you send the headers that
http://netix.dl.sourceforge.net/project/filezilla/FileZilla_Client/3.11.0.2/FileZilla_3.11.0.2_win64-setup.exe
returns? (Wondering what the Cache-control: header says about the caching
policy for that object).
miles
On Friday, January 29, 2016 2:02 AM, Muhammad Faisal
<[email protected]> wrote:
Hello,
I'm testing ATS v6.0. I'm seeing the cache hit ratio is low im seeing
too many TCP_MISS, TCP_IMS_MISS for the same websites which im trying to
reopen. Also if a file is downloaded form the internet it should be
available for the next request from the cache but im seeing direct
connection in the logs:
This file download was the second attempt to check if the content is
delivered from the Cache or not:
1454061387.378 123857 Client_IP TCP_MISS/206 6474156 GET
http://netix.dl.sourceforge.net/project/filezilla/FileZilla_Client/3.11.0.2/FileZilla_3.11.0.2_win64-setup.exe
- DIRECT/netix.dl.sourceforge.net application/octet-stream
1454061458.314 70774 Client TCP_MISS/200 6477302 GET
http://netix.dl.sourceforge.net/project/filezilla/FileZilla_Client/3.11.0.2/FileZilla_3.11.0.2_win64-setup.exe
- DIRECT/netix.dl.sourceforge.net application/octet-stream
Any advice to improve the situaiton?
Thanks
F.
