Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author SimonRWaters

    (@simonrwaters)

    Not tried it.

    Looks like the expectation is caching plugins should also cache headers but may not.

    https://github.com/szepeviktor/w3-total-cache-fixed/issues/219

    Perhaps it has had a regression, or change of heart?

    I’m a big fan of doing as much caching as possible via CDNs or reverse proxies.

    • This reply was modified 8 years, 5 months ago by SimonRWaters.
    Plugin Author SimonRWaters

    (@simonrwaters)

    Okay gave this a brief try. Looks like this plugin offers HSTS setting of its own, and offers some header management, but in general it is writing the content of the page into a long lived store to avoid rerendering, and in doing so the W3 Total Cache plugin thus loses page headers inserted with header command as the Security Headers plugin does.

    So it won’t work with the Security Headers plugin, or any other plugin that uses the same method to insert headers.

    In general I would recommend using a Content Delivery Network, or reverse proxy, and not complex WordPress plugins, to accelerate WordPress sites.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Does this work with W3 Total Cache?’ is closed to new replies.