Posted 6 months ago #
Redirection seems to work generally for me, but I'm confounded by one aspect.
In Options, I have "log 404 Not Found requests" checked and "log redirected requests" unchecked.
I deleted my log after that change to ensure that all I was seeing were 404s.
So, along with 404s being logged, I'm seeing some links to blog posts that work as-is being logged -- they don't trigger 404s. Why would these be logged if they're legitimate links?
Posted 6 months ago #
Upon further review, these links to legitimate posts that are displayed as 404s seem to be coming generally from the kind of miscreants that also do automated registrations on another site of mine.
I wonder... how can they be hitting a real post with the correct URL, and still be triggering a 404?
Any ideas?
Posted 5 months ago #
OK, I think I figured this one out...
These are 404s as a result of POSTs, not GETs.
I'm using the WP Captcha Free plugin, and apparently, it changes what is expected in the posting URL and thus leads automated spammers to a 404 page.
So, what I'm thinking is that it would be nice if the HTTP command that triggered the 404 was identified in the log, whether it's a GET or a POST.
You must log in to post.
