[wp-hackers] Re: wp-hackers Digest, Vol 47, Issue 77

baker god.dreams at gmail.com
Sat Dec 27 04:18:10 GMT 2008

Perhaps it may be for the IE Status 122 issue with GET?

Granted it depends on how much info is being pulled with "GET" but
I've hit the error before.


> ----------------------------------------------------------------------
> Message: 1
> Date: Fri, 26 Dec 2008 13:27:31 +0100
> From: Patrick Proniewski <patpro at patpro.net>
> Subject: Re: [wp-hackers] WP 2.7 : why using POST when GET is enough ?
> To: wp-hackers at lists.automattic.com
> Message-ID: <665FB2E0-25FC-4FD0-BA75-6A1807B1B485 at patpro.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
> Hi
> On 24 déc. 2008, at 22:46, Jacob Santos wrote:
>> Go to trac.wordpress.org and create a ticket. If you can, checkout
>> WordPress repository trunk directory. Make the change and submit the
>> patch to the same ticket.
> I don't really see the point in opening a ticket without knowing
> before if this is a bug or a design feature. May be the choice of POST
> instead of GET is made in an attempt to make WordPress more "RESTFul".
> But well, if nobody here knows about that, I figure I'll have to fill
> a bug report.
>> Patrick Proniewski wrote:
>>> Since version 2.7, WP uses POST method to request "wp-cron.php?
>>> check=...". What is the point ?
>>> My antispam filter works by denying POST method to people who fail
>>> to provide proper credentials. It's implemented on the server side
>>> (in httpd.conf). Then, the POST method is denied for wordpress or
>>> whatever process on the server.
>>> I had to edit wp-includes/cron.php to replace wp_remote_post with
>>> wp_remote_get.
>>> I need to get rid of every POST requests made locally, and replace
>>> them with GET requests.
> regards,
> patpro

More information about the wp-hackers mailing list