Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Lester Chan

    (@gamerz)

    How about if you don’t enter anything and click Save Changes? I think it might be a mod_security issue (https://www.modsecurity.org/) on your server conf.

    You might want to check the server error log to see if there is anything.

    Thread Starter SickSquirrel

    (@sicksquirrel)

    Same issue. Error logs are inundated with mod _security errors

    Examples

    [Tue Sep 17 15:58:08 2013] [error] [client 184.75.17.146] ModSecurity: Access allowed (phase 2). Pattern match “images/wordpress-logo.(?:jpe?g|gif|png)” at REQUEST_FILENAME. [file “/etc/httpd/conf.d/mod_security.conf”] [line “14”] [msg “WPImage”] [hostname “www..com”] [uri “/wp-admin/images/wordpress-logo.png”] [unique_id “k-VbyMy8ZAQAAHSWM4UAAAAV”]

    [Tue Sep 17 15:58:18 2013] [error] [client 184.75.17.146] ModSecurity: Access allowed (phase 2). Operator EQ matched 1 at IP:bf_counter. [file “/etc/httpd/conf.d/mod_security.conf”] [line “21”] [msg “BF SET”] [hostname “www..com”] [uri “/wp-login.php”] [unique_id “lI@o@cy8ZAQAAGbiGCUAAAAD”]

    [Tue Sep 17 16:53:31 2013] [error] [client 173.74.14.87] ModSecurity: Warning. Operator EQ matched 0 at GLOBAL. [file “/etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf”] [line “120”] [id “960903”] [msg “ModSecurity does not support content encodings”] [severity “WARNING”] [hostname “www..com”] [uri “/index.php”] [unique_id “WfNmFMy8ZAQAACNoKhkAAAAC

    I haven’t a clue what is causing my logs to fill up so logs sent to them. It worked fine on another site but I aren’t checked there yet

    Plugin Author Lester Chan

    (@gamerz)

    You might want to disable mod_security, personally I find it not very helpful and takes up a lot of resources.

    My host probably feels it is a security issue. I did email yesterday at this time, with the log, but no answer yet.

    What do the logs tel you? What does mod security really do?

    Plugin Author Lester Chan

    (@gamerz)

    mod_security does a lot of stuff, it blocks request it deems “insecure” from actually being parsed by Apache. Based on my experience at work, it blocks a lot of false positive as well and I don’t like it!

    Thread Starter SickSquirrel

    (@sicksquirrel)

    I see my IP in other logs but I’m allowed to do things! The logs above, to me, say someone tried to login but didn’t. (Probably a spammer) but also that the logo img tried to be shown and it wasn’t allowed. Content encoding sounds bad. Hopefully my host will respond. Great uptime but support is horrible.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bad Request’ is closed to new replies.