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 to change the method on the redirected request. So ICS is actually not RFC compliant for 302 HTTP relocation, may be this will be fixed in a next version or may be there is some compilation flag to allow it its sources ? Regards. FT> Hello Dod, FT> Yes AFAIK that's how IE works as well. There was a discussion of this FT> a few years ago on this list. IIRC, somebody else had complained at FT> that time too. FT> Best Regards, FT> SZ FT> On Mon, May 5, 2008 at 4:47 PM, Dod <[EMAIL PROTECTED]> wrote: >> 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 nothing into its $_POST array. >> >> Is this normal ? ICS should follow relocation with same GET/POST calls >> as the original call no ? >> >> regards. >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
