Buy commercial curl support from WolfSSL. 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
himself.
Re: Force content decoding
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Wolf Vollprecht via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 7 Jul 2022 11:19:13 +0200
Hi Timothe,
Thanks for your message. Indeed, I want to decode the data. The server is not broken (it’s the Github OCI registry server), I just cannot control what headers it sends for the binary blobs that I uploaded.
Ideally I would have wanted to re-use the internal libcurl functions for decoding that would be used if the server would reply with the correct Content-Encoding vs implementing it in my WRITEFUNCTION.
Best,
Wolf
> On 7. Jul 2022, at 11:15, Timothe Litt via curl-library <curl-library_at_lists.haxx.se> wrote:
>
>
> On 07-Jul-22 03:56, Wolf Vollprecht via curl-library wrote:
>> Hi all,
>>
>> I have some data that I am downloading where I know that it is gzip-encoded. However, the server does not respond with the correct header (and I don’t have control over it). I was wondering if there is a way to either “manually” append the proper Content-Encoding header to the response or force libcurl to encode the response with gzip?
>>
>> Best,
>>
>> Wolf
> I assume you mean "decode", not "encode". After the mandatory lecture about not tolerating broken servers...
>
> For the command line:
>
> curl https://foo.example.com/bar <https://foo.example.com/bar> | gunzip > data
>
> If you are using libcurl, depending on your requirements see zlib (libz) with CURLOPT_WRITEFUNCTION or popen() gunzip (or gzip -d).
>
>
>
> Timothe Litt
> ACM Distinguished Engineer
> --------------------------
> This communication may not represent the ACM or my employer's views,
> if any, on the matters discussed.
>
> --
> Unsubscribe: https://lists.haxx.se/listinfo/curl-library
> Etiquette: https://curl.se/mail/etiquette.html
Date: Thu, 7 Jul 2022 11:19:13 +0200
Hi Timothe,
Thanks for your message. Indeed, I want to decode the data. The server is not broken (it’s the Github OCI registry server), I just cannot control what headers it sends for the binary blobs that I uploaded.
Ideally I would have wanted to re-use the internal libcurl functions for decoding that would be used if the server would reply with the correct Content-Encoding vs implementing it in my WRITEFUNCTION.
Best,
Wolf
> On 7. Jul 2022, at 11:15, Timothe Litt via curl-library <curl-library_at_lists.haxx.se> wrote:
>
>
> On 07-Jul-22 03:56, Wolf Vollprecht via curl-library wrote:
>> Hi all,
>>
>> I have some data that I am downloading where I know that it is gzip-encoded. However, the server does not respond with the correct header (and I don’t have control over it). I was wondering if there is a way to either “manually” append the proper Content-Encoding header to the response or force libcurl to encode the response with gzip?
>>
>> Best,
>>
>> Wolf
> I assume you mean "decode", not "encode". After the mandatory lecture about not tolerating broken servers...
>
> For the command line:
>
> curl https://foo.example.com/bar <https://foo.example.com/bar> | gunzip > data
>
> If you are using libcurl, depending on your requirements see zlib (libz) with CURLOPT_WRITEFUNCTION or popen() gunzip (or gzip -d).
>
>
>
> Timothe Litt
> ACM Distinguished Engineer
> --------------------------
> This communication may not represent the ACM or my employer's views,
> if any, on the matters discussed.
>
> --
> Unsubscribe: https://lists.haxx.se/listinfo/curl-library
> Etiquette: https://curl.se/mail/etiquette.html
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-07-07