[trafficserver] branch 7.1.x updated: Deals better with Cc: max-age=0

[zwoop]

This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 7.1.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/7.1.x by this push:
     new ca558d8  Deals better with Cc: max-age=0
ca558d8 is described below

commit ca558d88d6579338b84cd4e888a8b3d7db01bc67
Author: Leif Hedstrom <zw...@apache.org>
AuthorDate: Thu Dec 6 08:58:00 2018 -0700

    Deals better with Cc: max-age=0
    
    There's a small window where we can still serve cached responses even
    when they have a Cache-Control: max-age=0.
    
    This fixes the cache-tests checks for id=freshness-max-age-0 and
    id=freshness-max-age-0-expires.
    
    (cherry picked from commit 0b80592bc472d5394c777d0fca66f72779276cf2)
    
     Conflicts:
        proxy/http/HttpTransact.cc
---
 proxy/http/HttpTransact.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/proxy/http/HttpTransact.cc b/proxy/http/HttpTransact.cc
index 2d66998..cacaf3e 100644
--- a/proxy/http/HttpTransact.cc
+++ b/proxy/http/HttpTransact.cc
@@ -7627,7 +7627,7 @@ HttpTransact::what_is_document_freshness(State *s, 
HTTPHdr *client_request, HTTP
   // now, see if the age is "fresh enough" //
   ///////////////////////////////////////////
 
-  if (do_revalidate || current_age > age_limit) { // client-modified limit
+  if (do_revalidate || !age_limit || current_age > age_limit) { // 
client-modified limit
     DebugTxn("http_match", "[..._document_freshness] document needs 
revalidate/too old; "
                            "returning FRESHNESS_STALE");
     return (FRESHNESS_STALE);