bryancall commented on issue #7136:
URL: https://github.com/apache/trafficserver/issues/7136#issuecomment-680146952


   I messed up on the copy and paste for the origin response and left out the 
max-age= in the cache control header.  ATS does the correct thing and ignores 
the Expires header in the presence of s-maxage and max-age.
   
   ```
   09:54:14 bart:/var/www/html$ curl -D - http://127.0.0.1:8080/expires.php
   HTTP/1.1 200 OK
   Date: Tue, 25 Aug 2020 16:49:44 GMT
   Server: ATS/10.0.0
   X-Powered-By: PHP/7.4.9
   Cache-Control: max-age=31536000, public
   Expires: Thu, 30 Jul 2020 15:18:11 GMT
   Content-Type: text/html; charset=UTF-8
   Age: 272
   Content-Length: 4
   Connection: keep-alive
   Via: http/1.1 traffic_server (ApacheTrafficServer/10.0.0 [uScRs f p eN:t 
cCHp s ])
   
   xxx
   09:54:16 bart:/var/www/html$ traffic_via 'uScRs f p eN:t cCHp s '
   Via header is [uScRs f p eN:t cCHp s ], Length is 22
   Via Header Details:
   Request headers received from client                   :simple request (not 
conditional)
   Result of Traffic Server cache lookup for URL          :in cache, fresh Ram 
hit (a cache "HIT")
   Response information received from origin server       :no server connection 
needed
   Result of document write-to-cache:                     :no cache write 
performed
   Proxy operation result                                 :unknown
   Error codes (if any)                                   :no error
   Tunnel info                                            :no tunneling
   Cache Type                                             :cache
   Cache Lookup Result                                    :cache hit
   Parent proxy connection status                         :no parent proxy or 
unknown
   Origin server connection status                        :no server connection 
needed
   ```


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to