4 ms·

Writing by default is logically followed by stderr? I just don’t follow. Asking a program for info and then getting that info on stderr seems really bizarre to

• unilynx 7y ago
  A lot of command line tools send debugging output to stderr so you can build a pipe/redirect output and still see the debug and error outputs. You could consider headers to be some sort of debug prints..
• Arnavion 7y ago
  >Asking a program for info and then getting that info on stderr seems really bizarre to me. The info that you're asking the program for is the response body. You're using `curl` / `curlie` primarily to get the response body and then pipe it to the rest of the command. The headers are ancillary. If the headers were the info you were asking for, eg when running `curl -D -`, then yes they should get printed to stdout. That is not the case being considered here.
• poitrus 7y ago
  It's convenient to have stdout only returning the body so you can work with it without having to remove the header. With curl, if you pass the -v, you get headers on stderr too. When headers are specifically requests with -i for instance, I agree curlie should print them on stdout. PR accepted ;)