That's extremely helpful to know Joshua. If what you say is true, that the METHOD shown access log is an exact copy of what is sent by the client (and by implication can't have been modified in any way by Apache), then that effectively rules out problems at the server end. The examples I sent you were all associated with failures of the application to receive data. In other words, every time the application fails to receive data, we get a log entry such the examples I gave and we are getting no 300 errors for this application.
So this seems to mean that although our application within the client is sending via POST, whether by simple HTML forms or via an embedded Flash application, the browser is sending it on as GET. And as I mentioned in the original post, I'm pretty sure our application isn't getting broken as I have been spending the last few days trying as hard as I can to break it with various combinations of data. I think this means that I have to go back to investigating the IE autoupdate which came out a couple of days before the problems began. Though I would still welcome comments from anyone in the list who has further ideas about this - either at the server end or the browser end. Thanks John ----- Original Message ----- From: Joshua Slive To: users@httpd.apache.org ; John Gosling Sent: Friday, May 18, 2007 4:42 PM Subject: Re: [EMAIL PROTECTED] GET requests being changed to POST On 5/18/07, John Gosling <[EMAIL PROTECTED]> wrote: > In all cases, the > request was sent as POST. No, what you see in the access_log is an exact copy of the request line sent from the client. So the client is sending GET. That still leaves the question: why? What you need to look at is the sequence of requests from the same client leading up to this problem request. Check to see if there is a POST request with a 3xx response. Joshua.
