asherwolf7

I posted this on my other thread, but I thought I’d post this here too.

The problem for me was my web server. The 404 error code was being generated by an actual 406 error code. 406 error codes are usually generated by mod_security, a module that exists on many web servers server-software (apache). This module filters all post requests and other things according to a set of rules. So, as soon as I’d post something to the wp-admin directory that wasn’t whitelisted it would fail. But it wasn’t a 404, but a 406. I determined this by temporarily disabling my index.php file and cUrling the server for an unadulterated result (the index.php page wasn’t able to handle the 404).

For some people the solution is to put a mod_security exception into an .htaccess file either at the top directory, or the wp-admin directory. I tried that, in several forms, but it either didn’t work, or gave me a 500 internal server error. Unfortunately this is not really the best option anyway as it can expose your website to troublesome atack-traffic.

Finall the solution for me was to contact my hosting company through a ticket aboud their mod_security set up. Since they were interested in keeping my business they modified the mod_security rules to allow this type of traffic (I don’t know the details) and now my proofreading post to wp-admin/admin-ajax.php?action=proxy_atd&url=/checkDocument works beautifully across my whole server.

Hope this helps the next guy, I spent all day on this.

Asher

SOLVED:

I finally tracked the error down to not a 404 error, but a 406 error. My host had mod_security on their server. I tried to turn it off with .htaccess files, but it was no use, it wouldn’t work. It was blocking all my post requests to anything in wp-admin mod_security didn’t show up on the phpinfo or phpinfo(INCLUDE_INFO) either. I finally contacted my hosting company with the specific problem (the proofreading URL and the inability to access posting on virtually all of my wp-admin directory outside of posting).

They ended up fixing it. This comes up because of a 406 error, at least in my case it did, but 406 will default to a 404 which will bring up the blog response.

Thanks for your help guys, and I hope this can help the next guy!

Asher

Turns out, I can’t get any post data to admin-ajax.php

As soon as it has a post body, it returns a 404

In fact, I never noticed before, but I this is the same result on all my sites, despite their version, on my server.

This is using cUrl and hurl.it Maybe I’m missing something, like it has to be from the same domain name?

This is really frustrating.

I have been able to curl properly when it’s just the URL (https://www.furtuber.com/wp-admin/admin-ajax.php?action=proxy_atd&url=/checkDocument), but as soon as I curl with –data ‘key=blah&data=text’ it 404s on me.

I have the following installed:

Akismet
Disabler
Fast Secure Contact Form
Featured Image Via URL
Google XML Sitemaps
Hello Dolly
Jetpack by WordPress.com
Select RSS Multi Importer
Twitter Mentions as Comments

Only Akismet and Jetpack are active.

I have also tried to edit the jquery.atd so that it sends no data with the request, but I still get the same error.