Removed GZIP from Custom Code and now getting 403 errors.

  • Resolved alanpae

    (@alanpae)


    12 years, 9 months ago

    Click on Custom Code.

    Click on Root htaccess File Custom Code

    Scroll down to:

    CUSTOM CODE BOTTOM HOTLINKING/FORBID COMMENT SPAMMERS/BLOCK BOTS/BLOCK IP/REDIRECT CODE: Add miscellaneous code here

    Remove the following lines:

    #Enable gzip compression
    <IfModule mod_deflate.c>
    AddOutputFilterByType DEFLATE text/html text/xml text/css text/plain
    AddOutputFilterByType DEFLATE image/svg+xml application/xhtml+xml application/xml
    AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml
    AddOutputFilterByType DEFLATE text/javascript application/javascript application/x-javascript
    AddOutputFilterByType DEFLATE application/x-font-ttf application/x-font-otf
    AddOutputFilterByType DEFLATE font/truetype font/opentype
    </IfModule>

    Click Save Custom Root Code

    Click Security Modes

    Click create secure htaccess file

    Click Activate Security Modes – BulletProof Mode

    Try to access the website.

    403 Forbidden Error

    Version is the latest of BulletProof

    Please suggest a fix.

    In the meantime I’ve hand edited .htaccess and removed the lines.

    http://ww.wp.xz.cn/plugins/bulletproof-security/

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    Double check all of the Root Custom Code text boxes to ensure that there are not any invalid entries (code, text or blank spaces) in any of the text boxes.

    plain text needs to be commented out with a pound sign # and there should not be any blank spaces in Custom Code text boxes.

    # Example plain text commented out – I am a teapot

    Code must be valid .htaccess code in the Custom Code text boxes. If it is not or a typo exists then you will see 403 errors.

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    In order to allow the widest range of .htaccess code manipulation/use/customization in BPS Custom Code we are not using the php trim() function, otherwise this would limit personalizing/customizing custom code for folks.

    trim( $variable, " \t\n\r");

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    No Dice.

    I went through each of the locations and made sure nothing was in them. I modified the custom code section at the bottom and added # to all blank links.

    Same error. Error log shows nothing.

    What’s next?

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    Remove all the # signs. When you add a # sign this means remove this entire section of .htaccess code from being created in your root .htaccess file or in other words either your site will crash or it will be broken or you will just see 403 errors.

    All of the Custom Code text boxes should be blank, unless you are adding actual custom .htaccess code in them. Some Custom Code text boxes require that you copy the entire sections of .htaccess code from your root .htaccess file in order for them to work correctly. Click the Video Tutorial link on the Custom Code page to see how this is done.

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    The secure.htaccess file looks ok to me. Leave an email address and I’ll email it to you and you can tell me what’s wrong with it.

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    oops I think I may be misinterpreting what you mean/said.

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    info [at] ait-pro [dot] com

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    Someone from Go Daddy must be reading this. When I can get access to the File Manager again I’ll send the file.

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    Now I know they’re reading this. File Sent. 🙂

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    Please send the actual file instead of copying and pasting the code into an email. I see a jumble of code that is not formatted. I did see some mistakes right away.

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    attached file sent.

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    Thanks for the edit and the explanation. Should I just delete the other one then altogether?

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    I stripped out all the old code that Better WP Security is still using from an ancient version of BPS. Current versions of BPS have .htaccess code that is light years ahead of what Better WP Security is still using. Also stripped out any other redundant or outdated code in the file that you sent me. I do not recommend using the that last part of the code where i added comments and instead use the code in link i posted for code that actually really works. 😉

    Plugin Author AITpro

    (@aitpro)

    12 years, 9 months ago

    we were posting at the same time so the answer is yes. Use the code we created in the link I added in the comments and lose that crap code. 😉

    Thread Starter alanpae

    (@alanpae)

    12 years, 9 months ago

    That allowed the web site to work but causes 500 errors on the admin pages. So I just removed all of their code altogether.

    Everything works again. 🙂

    Thanks,
    alan

    Marking as resolved.

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

The topic ‘Removed GZIP from Custom Code and now getting 403 errors.’ is closed to new replies.

Tags