> The @ construct lets you get POST data from a file

I understand that. I was hoping for a way to simply say "these data are
for PUT rather than POST" and being able to use the whole --data
machinery, but that's just me being biased with my needs for REST right
now :-) It doesn't really make sense otherwise. I can always have my
scripts write the PUT data into a temp file, or pipe both PUT and POST
data into curl.

YA

­­­
Learn about GPT services and architectures on Confluence.
<http://confluence/display/GPT/GPT+Architecture>

On 1/17/13 10:55 PM, "Dan Fandrich" <dan_at_coneharvesters.com> wrote:

>On Thu, Jan 17, 2013 at 03:07:25PM -0800, Yves Arrouye wrote:
>> This requires file names, correct? Maybe that's why people using curl
>>for
>> REST services start with a -X PUT and then just go "-X <method>" for
>> everything?
>
>The @ construct lets you get POST data from a file. There's seldom a
>legitimate
>reason to use -X for normal web traffic.
>
>>>> Dan
>-------------------------------------------------------------------
>List admin: http://cool.haxx.se/list/listinfo/curl-library
>Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-01-18