• Resolved yhthn

    (@yhthn)


    Hello,

    I am using CompressX on a website with Cloudflare enabled.

    Even though I check and save the option
    “Remove Header always set Cache-Control "private" from .htaccess file”,
    the following line is not removed from the wp-content/.htaccess file:

    Header always set Cache-Control "private"

    • The line remains after saving the settings
    • Even if I manually remove it from .htaccess,
      CompressX adds it back automatically
    • Because of this, Cloudflare shows cf-cache-status: BYPASS
    • Pages cannot be cached as public by Cloudflare

    For a Cloudflare-enabled site, forcing Cache-Control: private
    causes CDN cache and SEO performance issues.

    My questions:

    • Is this a bug?
    • Why is the header rewritten even when the option is enabled?
    • How can Cache-Control: private be completely disabled for Cloudflare users?


    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support johnghiz

    (@johnghiz)

    Hello @yhthn

    Thanks for your feedback.

    We have confirmed that this is a bug caused by the V2 interface failing to save this specific setting. Our team will include a permanent fix for this in the next public release.

    To resolve this immediately, you can temporarily switch back to the V1 interface by going to General Settings, selecting Change Style, choosing Old Style, and clicking Save Changes. Once in the V1 interface, enable the option to Remove ‘Header always set Cache-Control “private”‘ from .htaccess file. Once you have saved the change in V1, you can switch back to the V2 interface and the setting will remain active.

    All the best,

    Thread Starter yhthn

    (@yhthn)

    Hello,

    Thank you for your quick response and for clearly identifying the issue and providing a working, correct, and reliable solution.
    The workaround you shared resolved the Cloudflare cache issue immediately.

    We also appreciate that this will be permanently fixed in the upcoming release.
    Thanks again for your support and great work.

    Best regards,

    Plugin Support johnghiz

    (@johnghiz)

    Hello @yhthn

    You are welcome, and thanks again for reporting the issue.

    Please let us know if you need any further information or assistance.

    All the best,

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

You must be logged in to reply to this topic.