amoghyermalkar123 commented on issue #8672: URL: https://github.com/apache/trafficserver/issues/8672#issuecomment-1101427577
for cache.config url_regex=domain.com/* method=GET method=HEAD revalidate=1s and max-age header from origin server came in as 2 seconds. We have configured ATS to not ignore cache control max-age header as well. (via following config - proxy.config.http.cache.ignore_client_cc_max_age) so now - with the following request sequences, seperated by a few seconds apart - 1 ``` curl -v -H 'X-Debug: X-Cache' https://domain.com/ <X-Cache: miss, Miss from origin ``` 2 ``` curl -v -H 'X-Debug: X-Cache' https://domain.com/ <X-Cache: hit-stale, Miss from origin ``` 3 ``` curl -v -H 'X-Debug: X-Cache' https://domain.com/ <X-Cache: hit-fresh, Miss from origin ``` 4 - this is a few minutes apart ``` curl -v -H 'X-Debug: X-Cache' https://domain.com/ <X-Cache: hit-fresh, Miss from origin ``` We have a live HLS file, which is updated every 2 seconds, but due to ATS's current nature playback cannot proceed since ATS constantly gives the same response instead of going to the origin server and fetching the latest `index.m3u8` file. Please note that the `index.m3u8` file lies at the same path and is updated at the same path every time, hence the origin server url stays the same every time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
