• Resolved Adam

    (@adamlachut)


    Hi,

    Are you planning to restore 6G .htaccess rules for users who do not want to use your .php firewall?

    I hope you understand that someone may prefer another WAF solution than yours.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @adamlachut

    Let me create internal ticket for this and get back to you. Main reason to move from .htaccess to php is the .htaccess is not supported by nginx etc server ..

    Regards

    Thread Starter Adam

    (@adamlachut)

    This change has affected users for whom these rules were working.

    With the removal of the 6G rules from .htaccess, these users have been de facto forced to use your PHP-based firewall.
    But:

    • we are not familiar with its effectiveness…
    • this solution is based on PHP and not .htaccess, which has traditionally been the first line of defense
    • this change prevents the use of other, proven / favorite / premium WAFs that may already be installed on our systems

    Please consider the possibility of restoring the 6G (or newer) .htaccess rules for users who do not wish to use your PHP firewall.

    I hope you understand that users may have different preferences for their WAF solutions.

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi Adam,

    Sorry for late reply.

    The goal is to move away from htaccess, users can easily just copy and paste the htaccess rules from the 6g website if they still want them.

    WP Security > Firewall > Custom rules there they can add the htaccess rules.

    Regards

    Thread Starter Adam

    (@adamlachut)

    users can easily just copy and paste the htaccess rules from the 6g website if they still want them.

    No, usually they don’t. Most web servers should block POST with that kind of content with 403 and messages from server WAF like “LDAP Injection Attack” or similar.

    Additionally, there is still 6g settings section in AIO Security settings what is, at least, confusing.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘6G .htaccess rules in 5.x versions’ is closed to new replies.