Sounds good.
Thanks.
-Matthew Ring
-Original Message-
From: Ross Rankin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2003 1:26 PM
To: 'Commons HttpClient Project'
Subject: RE: redirects not allowed for PostMethod
Just as a FYI, as a workaround I would get the hea
t Project'
Subject: RE: redirects not allowed for PostMethod
Oleg,
Yes, I read some of the other posts after responding and saw that there is
the difficultly you mention.
My usage of the HTTPClient wraps the submit functionality to provide
redirect functionality and returns the method objec
good enough for posting, but worked
for what I was doing.
Sincerely,
James.
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2003 11:06 AM
To: Commons HttpClient Project
Subject: RE: redirects not allowed for PostMethod
James,
I can't say
ames.
>
>
> -Original Message-
> From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 17, 2003 3:01 PM
> To: Commons HttpClient Project
> Subject: Re: redirects not allowed for PostMethod
>
> Hi Matthew
>
> We have had quite a bit of ar
3:01 PM
To: Commons HttpClient Project
Subject: Re: redirects not allowed for PostMethod
Hi Matthew
We have had quite a bit of argument regarding automatic POST redirects a
while ago
http://www.mail-archive.com/commons-httpclient-dev%40jakarta.apache.org/msg0
1116.html
If you disagree with the conc
On Tuesday, March 18, 2003, at 07:16 AM, Jeffrey Dever wrote:
I'd say that a post redirect converted to a get is good behaviour to
add as part of the redirect overhaul as discussed for httpclient 3.0
I would say such behaviour is fine as long as it can be turned off on a
per request basis.
--
M
: Commons HttpClient Project
Subject: Re: redirects not allowed for PostMethod
Jeffrey Dever wrote:
> I'd say that a post redirect converted to a get is good behaviour to add
> as part of the redirect overhaul as discussed for httpclient 3.0
The problem of this scenario is:
- you tell Ht
Jeffrey Dever wrote:
I'd say that a post redirect converted to a get is good behaviour to add
as part of the redirect overhaul as discussed for httpclient 3.0
The problem of this scenario is:
- you tell HttpClient to execute a POST
- it is redirected and executes a GET automatically
- but the appl
I'd say that a post redirect converted to a get is good behaviour to add
as part of the redirect overhaul as discussed for httpclient 3.0
Tom Samplonius wrote:
On Mon, 17 Mar 2003, Matthew S. Ring wrote:
...
conflicts with RFC 2616. Is this stringency really neccesary? Selfishly, it
...
On Mon, 17 Mar 2003, Matthew S. Ring wrote:
...
> conflicts with RFC 2616. Is this stringency really neccesary? Selfishly, it
...
I think there is some confusion about RFC2616 and redirected POSTs.
RFC2616 says that POSTs should not be redirected, and no one really does
that. All current web
Matt,
I went through the same thing a week or two ago. Thing is, what method
should the PostMethod use for the redirect? You need to capture the
result and issue a GET using the Location response header attribute.
David
Matthew S. Ring wrote:
Hi,
I just started using the latest version of the
Hi Matthew
We have had quite a bit of argument regarding automatic POST redirects a
while ago
http://www.mail-archive.com/commons-httpclient-dev%40jakarta.apache.org/msg01116.html
If you disagree with the conclusion we arrived at, feel free to file a
bug report. We would not mind providing this
Hi,
I just started using the latest version of the HTTPClient to screen-scrape
from Rational Clear Quest. Unfortunately, CQ expects POSTed requests and
responds with a redirect. IE and Mozilla-based browsers seem OK with that,
but the HTTPClient refuses to follow redirects after a POST, due to sta
13 matches
Mail list logo
