On Sun, 2 Mar 2025, Bastian Jesuiter wrote:
I personally like the idea of adding a flag specifically for this new -L
behavior.
Here's a first take that introduces a --request-mode option for this purpose:
https://github.com/curl/curl/pull/16543
--
/ daniel.haxx.se || https://rock-solid.cur
I personally like the idea of adding a flag specifically for this new -L
behavior.
Or alternatively change the default -L behavior.
I think that this might become a new default, that any response might be
used to return a specific / custom METHOD to use in redirected / subsequent
requests, unrela
On Tue, 25 Feb 2025, Daniel Stenberg wrote:
This new functionality that opens up the opportunity to make curl do QUERY
better by using this new flag. But how?
My plan is now to merge the libcurl part necessary for this functionality in
this feature window, then write up a proposal for the cur
> Am 25.02.2025 um 15:19 schrieb Daniel Stenberg via curl-users
> :
>
> On Tue, 25 Feb 2025, Daniel Stenberg via curl-users wrote:
>
>> 4. Another way?
>
> I thought of another way:
>
> 4. Add a new option --location-code that just changes how -L works, so that
> users can opt to add this
On Tue, 25 Feb 2025, Stefan Eissing wrote:
AFAICT, this is to make QUERY requests working correctly? Would it be
clearer to have a separate option to do a QUERY, which then would have the
"correct" redirect behaviour? So, user would not have to -X this?
While the primary purpose right now is
On Tue, 25 Feb 2025, Daniel Stenberg via curl-users wrote:
4. Another way?
I thought of another way:
4. Add a new option --location-code that just changes how -L works, so that
users can opt to add this in their .curlrc and magically have all existing
command lines using -L switch over