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: Feature request: Add 'content' field in -w %{json} output
- 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: Wed, 23 Feb 2022 13:52:06 -0700
On Feb 23, 2022, at 13:02:28, rs _ wrote:
> ...
> For a single property (or a few properties) -> -w '{content_type}'
> For general metadata -> -w '{json}'
> For the entire response -> -w '{json+full}' (or something like that)
>
> > Try that with a terrabyte download! =)
>
> It wouldn't work and that's the reason I think this should be implemented in curl.
>
I haven't followed this thread closely, but was there an objection
to piping normal curl output through a json filter?
(Is the "--dump-header <filename>" output available early enough
for a filter to base decisions on it.?)
Date: Wed, 23 Feb 2022 13:52:06 -0700
On Feb 23, 2022, at 13:02:28, rs _ wrote:
> ...
> For a single property (or a few properties) -> -w '{content_type}'
> For general metadata -> -w '{json}'
> For the entire response -> -w '{json+full}' (or something like that)
>
> > Try that with a terrabyte download! =)
>
> It wouldn't work and that's the reason I think this should be implemented in curl.
>
I haven't followed this thread closely, but was there an objection
to piping normal curl output through a json filter?
(Is the "--dump-header <filename>" output available early enough
for a filter to base decisions on it.?)
-- gil -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-02-23