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
|