• Resolved tober1

    (@tober1)


    Hi,
    The wordfence website advises the following addition to .htaccess to deal with litespeed updating issues: Find the line that says “# BEGIN WordPress” and add this code above it:

    # BEGIN litespeed noabort
    RewriteEngine On
    RewriteRule .* – [E=noabort:1]
    # END litespeed noabort

    My htaccess starts with
    # BEGIN LSCACHE
    # END LSCACHE
    # BEGIN WordPress

    So where does the recommended line go? before or after the # BEGIN WordPress?

    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • I don’t quite understand why you’re asking this, as the WF says place above #BEGIN WordPress so that would mean your .htaccess would end up looking like this:

    # BEGIN LSCACHE
    # END LSCACHE
    # BEGIN litespeed noabort
    RewriteEngine On
    RewriteRule .* – [E=noabort:1]
    # END litespeed noabort
    # BEGIN WordPress

    MTN

    Thread Starter tober1

    (@tober1)

    Thanks for your response. My question was perfectly clear and justified. No reference was made to any entries above # BEGIN WordPress in the WF info.

    Just trying to help.

    My question was perfectly clear and justified. No reference was made to any entries above # BEGIN WordPress in the WF info.

    Umm… no, it was neither clear nor justified…
    You answered your own question in your own first post.

    Hi,
    The wordfence website advises the following addition to .htaccess to deal with litespeed updating issues: Find the line that says “# BEGIN WordPress” and add this code above it:

    Before you slam a solid contributor (MTN) to this forum with your rudeness, maybe you should think/read first – BEFORE you type.

    Hi @tober1,

    Can you confirm you’ve got Wordfence up and scanning on your site?

    *************************************

    @mountainguy2, @bluebearmedia,

    Thanks for helping out!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Wordfence Security – Litespeed .htaccess info’ is closed to new replies.