Timeline for Getting curl to output HTTP status code?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2023 at 16:18 | comment | added | MichaelM |
As of 2021 you can now use the --fail-with-body option
|
|
| Apr 28, 2020 at 13:11 | comment | added | Lucas Cimon |
Thanks to a colleague, I discovered --fail --show-error
|
|
| Aug 29, 2019 at 8:47 | comment | added | Logan Mzz | As stated in documentation, it doesn't work for 401 and 407 HTTP code :( | |
| May 13, 2018 at 23:33 | comment | added | jamshid | Agreed, not being able to see the error output is a painful limitation of the otherwise very handy --fail. How can you diagnose a REST api failure without seeing the error output? It's so unfortunate that the curl maintainer bagder stubbornly insists on not providing a --fail-but-show-error. github.com/curl/curl/issues/1978 | |
| May 23, 2017 at 12:41 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Mar 20, 2017 at 10:17 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Apr 6, 2016 at 13:59 | history | edited | Lucas Cimon | CC BY-SA 3.0 |
added 86 characters in body
|
| Apr 6, 2016 at 13:08 | history | answered | Lucas Cimon | CC BY-SA 3.0 |