404 enabled by default as bug fix?

  • Resolved Samuel Aguilera

    (@samuelaguilera)


    9 years, 9 months ago

    Hi!

    In latest release you have added the following to the changelog:

    Bug Fix
    Enabled the 404 logging by default during upgrade and new install. Read this FAQ for more information on this functionality.

    I wonder why are you considering enabling 404 logging by default on new installs and also in upgrades as a bug fix. What’s the point of doing that?

    404 error logging can increase the site load a lot on sites with a high number of visits where bots are hitting the site constantly (e.g. dummy bots trying to find if you’re using any of the vulnerable software in its database).

    It should not be enabled by default, at least in upgrades.

    Regards.

    https://ww.wp.xz.cn/plugins/wp-security-audit-log/

Viewing 1 replies (of 1 total)
  • WPWhiteSecurity

    (@wpwhitesecurity)

    9 years, 9 months ago

    Hello Samuel,

    Thank you for your feedback and for showing interest in our plugin.

    When we released the plugin update that alerts the user of 404 requests, many asked us to log these requests. When we did, many got confused because the plugin was not logging the requests, since it had to be activated manually. So this whole thing created a bit of a confusion.

    That is why we issued a release that enables the logging by default however please note that:

    1. The logging is capped to 99 requests, enough to give the user a good idea of what the source is up to without affecting the website’s performance and consuming too many resources.

    2. This was the only update that enabled these options by default. Moving forward the updates won’t change such options.

    While I trust the above gives you a better overview of the situation, please do not hesitate to get in touch should you have any further queries.

Viewing 1 replies (of 1 total)

The topic ‘404 enabled by default as bug fix?’ is closed to new replies.