On Thu, 23 Feb 2017, corey kasten wrote:

>> I wouldn't mind seeing that supported withot having to use
>> CURLOPT_CUSTOMREQUEST, no.
>
> Sorry, I couldn't tell whether you mean you would like to see that supported
> and therefore *would* consider a feature request, or "no", you wouldn't want
> it supported because it's unnecessary due to CURLOPT_CUSTOMREQUEST allowing
> it to be worked around...

I actually don't care much for feature requests. It is very easy to have ideas
and to ask for features but having a large set of requested features don't
improve much for anyone. Actually making the feature happen is what takes
skills, time and energy.

I wouldn't mind if someone wrote code and introduced this sort of
change/feature that would let an application to do PUT with CURLOPT_POSTFIELDS
slightly nicer in libcurl. It could even be made in a way that made use of
CURLOPT_CUSTOMREQUEST but perhaps with a way to set the custom request only
for the first request and made following ones respect 30X responses for
redirect follows. Or something.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html