{"id":39300,"date":"2026-07-07T03:35:00","date_gmt":"2026-07-06T20:35:00","guid":{"rendered":"https:\/\/dps.media\/sua-loi-cloudflare-khong-cache-trung-lap-cache-control-no-cache\/"},"modified":"2026-07-07T03:35:00","modified_gmt":"2026-07-06T20:35:00","slug":"fix-cloudflare-not-caching-always-revalidated-expired-due-to-duplicate-cache-control-no-cache","status":"publish","type":"post","link":"https:\/\/dps.media\/en\/fix-cloudflare-not-caching-always-revalidated-expired-due-to-duplicate-cache-control-no-cache\/","title":{"rendered":"Fix Cloudflare not caching (always REVALIDATED\/EXPIRED) due to duplicate Cache-Control: no-cache on OpenLiteSpeed and Nginx Reverse Proxy"},"content":{"rendered":"

One of the common issues preventing Cloudflare from caching a website (always returning status REVALIDATED<\/code> 5px EXPIRED<\/code> instead of HIT<\/code>) is the presence of the header Cache-Control: no-cache<\/code> from the origin server. This article will guide you through detailed diagnosis and a complete fix for this issue on systems using Nginx as a Reverse Proxy in front of OpenLiteSpeed.<\/p>\n

1. Symptoms of the issue<\/h2>\n

When checking the Response Headers of your website or static files (such as CSS, JS, and images) using the curl command or Developer Tools (F12) in your browser, you see the following headers appearing at the same time:<\/p>\n

Cache-Control: public, max-age=2592000\nCache-Control: no-cache\nCf-Cache-Status: EXPIRED (or REVALIDATED)<\/code><\/pre>\n
The simultaneous presence of two conflicting Cache-Control<\/code> headers confuses Cloudflare. The no-cache<\/code> header forces Cloudflare to send a revalidation request to the origin server on every visit, increasing response time (TTFB) and overloading your origin server.<\/p>\n
2. Diagnosis process and root-cause identification<\/h2>\n
To resolve this issue completely, we need to go through steps to isolate the cause:<\/p>\n
    \n
  • Step 1: Check plugins and .htaccess:<\/strong> Many people often assume the issue is caused by WordPress cache plugins (such as LiteSpeed Cache) or the .htaccess<\/code>. file. However, if you use OpenLiteSpeed, it usually ignores header configurations (such as mod_headers<\/code>) in the file .htaccess<\/code>.<\/li>\n
  • Step 2: Check the Origin Server IP directly:<\/strong> Run curl directly against the origin server IP (bypassing Cloudflare) to see which headers are generated at the server:\n
    curl -I -k -H \"Host: yourdomain.com\" https:\/\/[SERVER_IP]\/wp-includes\/css\/dist\/block-library\/style.min.css<\/code><\/pre>\n
        If the Server: nginx<\/code> header appears together with x-turbo-charged-by: LiteSpeed<\/code>, your system is definitely running an Nginx Reverse Proxy model in front of OpenLiteSpeed.\n  <\/li>\n<\/ul>\n
    3. Complete solution<\/h2>\n
    Step 1: Remove the hardcoded configuration line in Nginx<\/h3>\n
    When configuring a Reverse Proxy on control panels such as aaPanel, the system often automatically adds a cache-prevention line in Nginx to avoid dynamic-data issues for Node.js\/Python applications. You need to remove it.<\/p>\n
    Open the Nginx configuration file for the domain (usually located at \/www\/server\/panel\/vhost\/nginx\/yourdomain.com.conf<\/code>), find the configuration block location \/<\/code>:<\/p>\n
    location \/ {\n    proxy_pass http:\/\/127.0.0.1:8188;\n    ...\n    # DELETE OR COMMENT OUT THE LINE BELOW:\n    # add_header Cache-Control no-cache;\n}<\/code><\/pre>\n
    Then save and Restart Nginx<\/strong> (Restart Nginx).<\/p>\n
    Step 2: Disable the OpenLiteSpeed Cache Module (when using Cloudflare Page Cache)<\/h3>\n
    If you are using plugins such as Super Page Cache for Cloudflare<\/i> to manage caching on Cloudflare and local disk, disable the OpenLiteSpeed cache module to avoid conflicts.<\/p>\n
    Open the main OpenLiteSpeed configuration file (httpd_config.conf<\/code>) through the aaPanel interface, find the block module cache<\/code> and change:<\/p>\n
    module cache {\n    ls_enabled          0 # Change from 1 to 0 to disable the module\n    ...\n}<\/code><\/pre>\n
    Save and Restart OpenLiteSpeed<\/strong>.<\/p>\n
    4. Results after the fix<\/h2>\n
    After completing these two steps, run the check command again. You will see only one header remaining Cache-Control<\/code> valid from WordPress\/LiteSpeed, and Cloudflare will return the status HIT<\/strong> immediately on subsequent visits.<\/p>\n