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: Curl feature idea, download hash checking
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Ray Satiro via curl-users <curl-users_at_lists.haxx.se>
Date: Sat, 13 Jun 2026 09:24:59 -0400
On 6/12/2026 7:16 AM, Daniel Stenberg via curl-users wrote:
> On Fri, 12 Jun 2026, Ian Norton via curl-users wrote:
>
>> curl -O URL —-hash sha256:HASH_VALUE
>>
>> Does this sound like a good idea?
>
> It is an idea that is often brought up but has never been
> materialized. Is it good? I think it depends on how it is done so that
> in the end people would use it.
Many years ago I wrote CURLOPT_SHA256 / CURLINFO_SHA256 to calculate the
hash of the transfer body as received but there wasn't any interest so
it wasn't adopted see https://github.com/curl/curl/issues/1399
These days sha256 is more common and we have sha256 calculation code
already in libcurl. So that part would be easier. But to handle
partially downloaded data, resumed data, etc, is still a complication.
You can already pipe curl to sha256 for verification, and ghedo gives an
example in that issue of how to do it.
Basically if you can do the unix pipe style to an existing tool that can
handle it then is it worth putting that tool's functionality in curl, I
guess is the question. What I mean is like grep should be grep, curl
should be curl etc
Date: Sat, 13 Jun 2026 09:24:59 -0400
On 6/12/2026 7:16 AM, Daniel Stenberg via curl-users wrote:
> On Fri, 12 Jun 2026, Ian Norton via curl-users wrote:
>
>> curl -O URL —-hash sha256:HASH_VALUE
>>
>> Does this sound like a good idea?
>
> It is an idea that is often brought up but has never been
> materialized. Is it good? I think it depends on how it is done so that
> in the end people would use it.
Many years ago I wrote CURLOPT_SHA256 / CURLINFO_SHA256 to calculate the
hash of the transfer body as received but there wasn't any interest so
it wasn't adopted see https://github.com/curl/curl/issues/1399
These days sha256 is more common and we have sha256 calculation code
already in libcurl. So that part would be easier. But to handle
partially downloaded data, resumed data, etc, is still a complication.
You can already pipe curl to sha256 for verification, and ghedo gives an
example in that issue of how to do it.
Basically if you can do the unix pipe style to an existing tool that can
handle it then is it worth putting that tool's functionality in curl, I
guess is the question. What I mean is like grep should be grep, curl
should be curl etc
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2026-06-13