Duplicate max-age HTTP Header?

  • Hi, I noticed a problem when I checked the HTTP Header. I tested it on HTTP Header check website and it looks like;

    Cache-Control:
    max-age=3600, must-revalidate
    max-age=604800

    What might be causing this problem? My WP Super Cache plugin seems working (No Preload, No CDN).
    In .htaccess; I have common leverage browser caching code without ‘Header set Cache-Control’ though.

    Installed plugins;
    – Akismet Anti-Spam
    – Really Simple SSL and Pro
    – ShortPixel Image Optimizer
    – Sucuri Security – Auditing, Malware Scanner and Hardening
    – tagDiv Composer
    – UpdraftPlus – Backup/Restore
    – WP-Optimize
    – Yoast SEO
    – and WP Super Cache obviously.

    Please, feel free to check yourself.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Thread Starter supvalravn

    (@supvalravn)

    I think it’s because of Leverage Browser Caching. Wp Super Cache add “max-age=3600, must-revalidate” to headers. Then my Leverage Browser Caching code in .htaccess add max-age to headers. Currently second one shows ExpiresByType text/html “access 1 hour”. When I delete it then it shows ExpiresDefault “access 2 days” (I guess). So what should I do about it? Normally, WP Super Cache and Leverage Browser Caching using both of them should be okay, right? Maybe delete “IFModule” from Leverage Browser Caching code or just live with that? Or is there any solution? I’m not expert guy and I’m quite lost.

    • This reply was modified 6 years, 8 months ago by supvalravn.
Viewing 1 replies (of 1 total)
  • The topic ‘Duplicate max-age HTTP Header?’ is closed to new replies.