This is similar to #588, but simpler. Rather than wanting to be able to limit the header fields displayed based on configuration or criteria, it would be really useful to have a light or quiet response header option. A lot of data is in those headers, most of which isn't very informative unless you're specifically looking for something in, e.g., the content security policy or content type or whatever. Most of the time we really only care about the response status code. In some cases, e.g. 30x responses, you'd want a bit more information, like the Location header.
I often find myself needing to copy and paste a lot of output when working on documentation or capturing data for debugging purposes. I want to have the response status code, but I don't need all the other baggage. This means I start with this:
I then have to go back and delete all of the HTTP headers by hand so that the resulting text is readable.
Don't get me wrong, it's worlds better than curl ;) In fact, this is really the only suggestion I have for improving httpie, it's a fantastic tool and I'm grateful for all the work that's gone into it!
This is similar to #588, but simpler. Rather than wanting to be able to limit the header fields displayed based on configuration or criteria, it would be really useful to have a light or quiet response header option. A lot of data is in those headers, most of which isn't very informative unless you're specifically looking for something in, e.g., the content security policy or content type or whatever. Most of the time we really only care about the response status code. In some cases, e.g. 30x responses, you'd want a bit more information, like the Location header.
I often find myself needing to copy and paste a lot of output when working on documentation or capturing data for debugging purposes. I want to have the response status code, but I don't need all the other baggage. This means I start with this:
I then have to go back and delete all of the HTTP headers by hand so that the resulting text is readable.
Don't get me wrong, it's worlds better than curl ;) In fact, this is really the only suggestion I have for improving httpie, it's a fantastic tool and I'm grateful for all the work that's gone into it!