HI all,

Why does it need to become a get anyway.
If a POST was intended then it should probably be a POST i guess ;-)

one way is to keep on posting until an errorcondition is met and then
maybe backtrack a step and try a get.

The other way would be to leave curl on Location: with a special exit status and
let the
calling procedure decide how to continue. Then the only question is how to pass
the location:
from one call to another. (a bunch of extra options is then needed)

just my .02
regards,
Nico Baggus

-----Original Message-----
From: curl_at_contactor.se
Sent: Friday, January 26, 2001 08:36
To: Curl Mailinglist <curl_at_contactor.se>
Subject: Q: POST - Location - GET/POST

Hi

From the recent bug report
(http://sourceforge.net/bugs/?func=detailbug&bug_id=129815&group_id=976)

The following question has been raised:

 Is there a point to add an option that would make curl *NOT* revert to GET
after a POST and Location:?

Today, when you use a POST operation and tell curl to follow a Location:,
curl automatically switches to GET after the initial request and thus the
order of operation is: POST - Location - GET. Howard Gayle wants the
operation to be POST - Location - POST, which indidently was how curl
behaved all the way until curl 7.1 (I think, I haven't checked the exact
version).

Is there a point of adding this as a separate option? What if there's a
second location after the second POST, what is curl supposed to do then?

-- 
  Daniel Stenberg -- curl project maintainer -- http://curl.haxx.se/
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------