Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates
 64.233.162.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=pR92SavVeWx2neMAoG01iC3pHBDuBXGKkiMZ18Or8sa80RDH5JnfAx9AAnL3/LQDEMC+y/tV1PvIm7vpkM6hJ6nsTBGySO2mnNCrKCk+J7KC9KJo/8mljm4DVupfox1r7k+aHeqUaoKC68xC1THzKz8ppieaodYd+s5y0ADiG5c=
Message-ID: <e498c1660705180702s446c02aek88495a9edb86f666@mail.gmail.com>
Date: Fri, 18 May 2007 10:02:50 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org,
 "John Gosling" <johngosling@realneedsoftware.co.uk>
In-Reply-To: <00af01c79954$6b4a4300$2101a8c0@Evesham>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <00af01c79954$6b4a4300$2101a8c0@Evesham>
Subject: Re: [users@httpd] GET requests being changed to POST

On 5/18/07, John Gosling <johngosling@realneedsoftware.co.uk> wrote:
> Hi,
>
> We have a web application which had been running unproblematically for
> around 6 years until several days ago (approximately 10th May).  At this
> time we suddenly found that requests sent via POST were intermittently
> showing up as GET requests in the Apache access logs.  On each such occasion
> (around 10% of requests)  the application would fail as a consequence with
> none of the POSTed data reaching our scripts. On the remaining 90% of
> occasions the POST request were getting transmitted successfully.

So your subject line is backwards.

> (a) has their been a recent update of Apache or related software over the
> last 10 days which could possibly have caused this problem?

No. And in any case Apache doesn't auto-update, so it would need to be
the result of you specifically changing something in apache.

>
> (b) does anyone have any idea of what sort of process could alter a POST
> request from a browser in such a manner as it finishes up as a GET request
> without any posted data by the time it reaches a CGI scripts?  Incidentally,
> on this point, we are pretty certain that the form is not broken in any way
> and submits a valid POST request.

The most common reason for a POST to change to a GET is that the POST
is redirected. Check your logs for 3xx response codes and figure out
what is generating them.

It isn't clear if you are actually seeing GET or POST in your
access_log. Perhaps you can show us some of the contents of the
access_log.

In the worse case, you should trace exactly what is getting sent back
and forth to apache using something on the wire or something like
mod_dumpio:
http://httpd.apache.org/docs/2.2/mod/mod_dumpio.html

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org