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

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

commit 36177dcff5978aeef0f8ede554f3f6df5421824c
Author: Brian Neradt <[email protected]>
AuthorDate: Tue Jul 1 15:52:51 2025 -0500

    Make OCSP refresh messages debug logs (#12329)
    
    Boxes with OCSP configured typically have their logs containing many of
    these:
    
    ```
    $ tail diags.log
    [Jul  1 18:14:05.654] [ET_OCSP 0] NOTE: OCSP refresh started
    [Jul  1 18:14:05.654] [ET_OCSP 0] NOTE: OCSP refresh finished
    [Jul  1 18:15:05.649] [ET_OCSP 0] NOTE: OCSP refresh started
    [Jul  1 18:15:05.649] [ET_OCSP 0] NOTE: OCSP refresh finished
    [Jul  1 18:16:05.648] [ET_OCSP 0] NOTE: OCSP refresh started
    [Jul  1 18:16:05.648] [ET_OCSP 0] NOTE: OCSP refresh finished
    [Jul  1 18:17:05.644] [ET_OCSP 0] NOTE: OCSP refresh started
    [Jul  1 18:17:05.644] [ET_OCSP 0] NOTE: OCSP refresh finished
    [Jul  1 18:18:05.640] [ET_OCSP 0] NOTE: OCSP refresh started
    [Jul  1 18:18:05.640] [ET_OCSP 0] NOTE: OCSP refresh finished
    ```
    
    This is probably not generally helpful. There are error messages for
    OCSP failure scenarios. This patch downgrades these to debug logs.
    
    (cherry picked from commit 0f507722125c60e34d463336ab414393996387ba)
---
 src/iocore/net/OCSPStapling.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/iocore/net/OCSPStapling.cc b/src/iocore/net/OCSPStapling.cc
index 7946c78129..af6d9f1819 100644
--- a/src/iocore/net/OCSPStapling.cc
+++ b/src/iocore/net/OCSPStapling.cc
@@ -1295,7 +1295,7 @@ ocsp_update()
   TS_OCSP_RESPONSE *resp = nullptr;
   time_t            current_time;
 
-  Note("OCSP refresh started");
+  Dbg(dbg_ctl_ssl_ocsp, "OCSP refresh started");
 
   SSLCertificateConfig::scoped_config certLookup;
 
@@ -1338,7 +1338,7 @@ ocsp_update()
       }
     }
   }
-  Note("OCSP refresh finished");
+  Dbg(dbg_ctl_ssl_ocsp, "OCSP refresh finished");
   return OCSPStatus::OCSP_OK;
 }
 

Reply via email to