That's correct -- the action is not compliant with the RFC. The problem is
that IE changes the POST to a GET and some sites expect that action. In
effect, IE has become the de facto standard. If you change ICS to stay
with the POST, you'll break existing applications. You could add a
proper
Hell,
I found this note looking in RFC2068 :
When automatically redirecting a POST request after receiving a 302
status code, some existing HTTP/1.0 user agents will erroneously
change it into a GET request.
And in RFC2616 :
RFC 1945 and RFC 2068 specify that the client is not allowed
Hello Dod,
Yes AFAIK that's how IE works as well. There was a discussion of this
a few years ago on this list. IIRC, somebody else had complained at
that time too.
Best Regards,
SZ
On Mon, May 5, 2008 at 4:47 PM, Dod <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I call a page using POST with pa
Hello,
I call a page using POST with parameters. The page produce a 302
redirection answer from server.
Using "FollowRelocation:=true" ICS follow the redirection but
transform the original POST into a simple GET without any parameter.
So the php script at final location get nothin
