Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 3649 invoked from network); 7 Mar 2003 16:39:44 -0000 Received: from unknown (HELO KCCXOEX10.corp.kpmgconsulting.com) (57.80.136.22) by daedalus.apache.org with SMTP; 7 Mar 2003 16:39:44 -0000 Received: from kccxoex03.corp.kpmgconsulting.com ([57.80.136.6]) by KCCXOEX10.corp.kpmgconsulting.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 7 Mar 2003 16:40:48 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: post redirect Date: Fri, 7 Mar 2003 16:38:40 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: post redirect Thread-Index: AcLkxedP9qLpMPMkRRCRKg2AHBPfhgAASUSw From: "Kalnichevski, Oleg" To: "Commons HttpClient Project" X-OriginalArrivalTime: 07 Mar 2003 16:40:48.0468 (UTC) FILETIME=[4EB21140:01C2E4C8] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N David HttpClient is a library, whereas a browser is a totally different kind = of beast. RFC 2616 says the following: "... If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued ..." A well-behaving browser should provide the end user with a confirmation = dialog or a configuration option to automatically perform POST = redirects. HttpClient can't have that luxury, as it is not supposed to = be directly interacting with the end user. I am personally convinced = that POST redirect should be handled by the application that consumes = Httpclient's services. All it basically takes is a retry loop Does anyone see that differently? Cheers Oleg -----Original Message----- From: David Kavanagh [mailto:dak@dotech.com] Sent: Freitag, 7. M=E4rz 2003 17:24 To: commons-httpclient-dev@jakarta.apache.org Subject: post redirect I've been working with httpclient for a couple of days to build a Cocoon = transformer that helps me build pipelines to navigate web sites and=20 extract data. I've read the parts of RFC2616 that deal with redirects=20 and state they are automatic on the client only for GET and HEAD=20 methods. I know the JDC and a web site I wrote use POST for the login=20 form and issue a redirect as a response. Any browser I've tried this=20 with honors the redirect. I can send some test code I've been using to=20 test the automated login (that includes handling cookies). Anyway, I've observed browsers honoring the redirect on a POST, can't=20 httpclient be configured that way? Looking at the source code tells me=20 no. (I've been using 2.0 alpha 3). Thanks, David --------------------------------------------------------------------- To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org