Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: %{filename_effective but not transmit file?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Paul Gilmartin via curl-users <curl-users_at_lists.haxx.se>
Date: Thu, 12 Sep 2024 07:04:34 -0600
On 9/12/24 00:40, Daniel Stenberg via curl-users wrote:
> On Thu, 12 Sep 2024, Daniel Stenberg via curl-users wrote:
>
>> Since --head implies that the body is not saved, we can actually make this work fairly easy...
>
> Eh, no. I was not thinking right. It still needs to save the headers in that final name that it will not know until several headers have already arrived. So not *that* simple.
> .
I was not asking for an enhancement, rather only for the simplest,
quietest way to extract filename-effective for use in a second
call to curl.
I have been using a read-only output-dir to do this.
> Basically what we need to do is to make the tool keep the initial set of headers in memory first before it has decided what file name to use, then save all the headers in the file name once it knows. That would fix this limitation.
> .
... with attendant error-handling scenarios.
Date: Thu, 12 Sep 2024 07:04:34 -0600
On 9/12/24 00:40, Daniel Stenberg via curl-users wrote:
> On Thu, 12 Sep 2024, Daniel Stenberg via curl-users wrote:
>
>> Since --head implies that the body is not saved, we can actually make this work fairly easy...
>
> Eh, no. I was not thinking right. It still needs to save the headers in that final name that it will not know until several headers have already arrived. So not *that* simple.
> .
I was not asking for an enhancement, rather only for the simplest,
quietest way to extract filename-effective for use in a second
call to curl.
I have been using a read-only output-dir to do this.
> Basically what we need to do is to make the tool keep the initial set of headers in memory first before it has decided what file name to use, then save all the headers in the file name once it knows. That would fix this limitation.
> .
... with attendant error-handling scenarios.
-- Thanks, gil -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-09-12