WordPress.org

Ready to get started?Download WordPress

Forums

BulletProof Security
[resolved] Setting expires headers results in WP readme.html unprotected (4 posts)

  1. sysopsavant
    Member
    Posted 11 months ago #

    I've added expires headers to my root .htaccess.

    #Expire Header
    <FilesMatch "\.(ico|jpg|jpeg|png|gif|js|css|swf)$">
    ExpiresDefault "access plus 30 days"
    </FilesMatch>

    After which I get a red error that WP readme.html is not protected. Anyway to fix this?

    http://wordpress.org/extend/plugins/bulletproof-security/

  2. AITpro
    Member
    Plugin Author

    Posted 11 months ago #

    Most likely you added this custom code to the top of your BPS root .htaccess file. One of the checks that occurs to check if a BPS .htaccess file is in use is to check the top of the root .htaccess file for the BPS version number.

    Use BPS Custom Code and add your caching code in this Custom Code text box below, click the Save Root Custom Code button, go to the Security Modes page, click the Create secure.htaccess File button and activate Root Folder BulletProof Mode again.

    CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE: Add php.ini handler and/or plugin cache code here

    #Expire Header
    <FilesMatch "\.(ico|jpg|jpeg|png|gif|js|css|swf)$">
    ExpiresDefault "access plus 30 days"
    </FilesMatch>

    Also we have come up with some decent caching code in the link below, BUT this caching code has some conflicts with WP Super Cache .htaccess code (and probably with W3TC caching code). We are looking into that and will find a solution for this. Currently we are only using this caching code and not any caching plugins.

    http://forum.ait-pro.com/forums/topic/where-is-the-log/page/2/#post-7436

  3. sysopsavant
    Member
    Posted 11 months ago #

    Thanks a lot. That worked perfectly. I do have WP Super Cache running so I won't mess with the caching code just yet.

  4. AITpro
    Member
    Plugin Author

    Posted 11 months ago #

    Cool! And as it turns out the caching code we created does not cause or have a conflict with WPSC. The issue is a random corrupt cache issue with WPSC that we thought was being caused by our caching code, but the corrupt cache issue in WPSC just happens randomly by itself.

Reply

You must log in to post.

About this Plugin

About this Topic