0:00 Intro: curl as an HTTP client 0:40 HTTP GET Requests (with and without -X) 2:03 HTTP POST with inline body 3:08 Set custom Headers with -H 4:20 Read body from file (on POST and other requests with bodies) 6:37 curl verbose mode 7:48 Print nothing but the HTTP status code with -w and -o 9:20 Basic auth with the -u option 10:28 Set the basic auth header manually 11:32 Inspect headers with -I 12:10 Follow redirects 14:20 Accept invalid HTTPS certificates Note: At 4:05 I’m happy about the fact that we have a non-zero exit code. By default curl will not fail if the HTTP status is >299 as Long as the request was successful. To make curl on non-200 status codes you need to provide the -fail option.
Crisp and clear explanation. I Loved the entire playlist. The way you were progressively adding new concepts one upon the other was amazing. Thank you so much for this series of videos! Also, if you are looking for an idea for your next videos. You can teach how to rock the vim + terminal like you do, I saw magic while you were explaining.
Great video! Thank you for demonstrating. Would you be able to make a full dummies tutorial just on cURL (maybe PHP, javascript, or additional tools if necessary)? Particularly submitting post request and managing the cookies associated with them? I'm struggling submitting forms (even some login forms on some sites, like my propstream acct). It would be awesome to learn from you.
No editing involved. Make sure EDITOR= points to vim, then press Ctrl-X Ctrl-E to edit the line in vim. The behavior is slightly different between zsh and bash. After :wq zsh will have the command line filled, but not executed. On bash doing :wq will also execute the command directly.
Hi. So instead of using high level languages with a bunch of libraries we can use simple and archaic shell scripts or Linux tools? Ok. Can I assume that Linux shell is underrated and is Linux shell the way to go to learn to code for a sys admin? Thanks
Shell vs high-level language isn't the topic of this video. "The only" in the title refers to the omni-present cURL vs. other CLI http tools. Knowing cURL well (or at least it's basics) is an incredibly useful skill for anyone that works with http (and other) APIs. Whether you develop them, interact with them, debug them, etc. I'm not advocating for writing your entire web app client with bash. What I'm saying is that being able to quickly fire off an http request from the terminal is a very valuable skill that can a lot of time.
How can I save the output from the POST request? So for example I had to make a POST request with credentials and I get back a token. I want to store that token as I need it to make other API requests? Is there a way to store it in a variable?
Thanks. To download a file you either need to redirect the output into a file or specify an output file with -o. So you either do "curl -o foo.jpg somehost.com/foo.jpg" or you do "curl somehost.com/foo.jpg > foo.jpg". Both will download into a local file foo.jpg.
0:00 Intro: curl as an HTTP client
0:40 HTTP GET Requests (with and without -X)
2:03 HTTP POST with inline body
3:08 Set custom Headers with -H
4:20 Read body from file (on POST and other requests with bodies)
6:37 curl verbose mode
7:48 Print nothing but the HTTP status code with -w and -o
9:20 Basic auth with the -u option
10:28 Set the basic auth header manually
11:32 Inspect headers with -I
12:10 Follow redirects
14:20 Accept invalid HTTPS certificates
Note: At 4:05 I’m happy about the fact that we have a non-zero exit code. By default curl will not fail if the HTTP status is >299 as Long as the request was successful. To make curl on non-200 status codes you need to provide the -fail option.
Wow that's nice
Hey Man....found your channel today....this so wonderful, I wish you hadn't stopped making videos
This is pure gold!!
Thanks!
It is absulutly pure pleasure to learn with your videos! Keep it up
simplicity is important for this kind of tutorials, thanks for this video!
Crisp and clear explanation. I Loved the entire playlist. The way you were progressively adding new concepts one upon the other was amazing. Thank you so much for this series of videos!
Also, if you are looking for an idea for your next videos. You can teach how to rock the vim + terminal like you do, I saw magic while you were explaining.
U know these are the only options that i’ve been used in curl command
Great job buddy, thanks again
I learned a lot here! You clarified a whole new world for me!
This is very under rated, you are amazing!
An awesome video as always. Thanks for the effort. Keep them coming!
Great stuff! Congrats! Keep sharing, please.
Great video! Thank you for demonstrating.
Would you be able to make a full dummies tutorial just on cURL (maybe PHP, javascript, or additional tools if necessary)? Particularly submitting post request and managing the cookies associated with them? I'm struggling submitting forms (even some login forms on some sites, like my propstream acct).
It would be awesome to learn from you.
i never understand http verbs this videos sums it all really glad !
Great video Man,
Can you make a video on a setup like yours for vim, terminal, etc
Love this video!!!
How did you open vim during the middle of a command and have the stdin appear inside vim? Or is this just editing?
No editing involved. Make sure EDITOR= points to vim, then press Ctrl-X Ctrl-E to edit the line in vim. The behavior is slightly different between zsh and bash. After :wq zsh will have the command line filled, but not executed. On bash doing :wq will also execute the command directly.
@@kubucation I can't get this to work. What terminal are u using? iterm2?
cool stuff from super cool you! ;)
Thank you i have an idea now about curl
you are a superman. I like the Vim editor you are using. Do you install it with Yum?
Great content liked and subbed
Really useful, thank you!
How do you jump into vim to edit the terminal like that?
same question
I googled it:use the edit-and-execute-command,which means press ctrl-x first ,then press ctrl-e
@@zihuatanejo7741 Thanks for updating me!
@@zihuatanejo7741 saved the day
Thank you.
I had to add the -o /dev/null before the url. I kept getting options -o not known
Hi. So instead of using high level languages with a bunch of libraries we can use simple and archaic shell scripts or Linux tools? Ok. Can I assume that Linux shell is underrated and is Linux shell the way to go to learn to code for a sys admin? Thanks
Shell vs high-level language isn't the topic of this video. "The only" in the title refers to the omni-present cURL vs. other CLI http tools.
Knowing cURL well (or at least it's basics) is an incredibly useful skill for anyone that works with http (and other) APIs. Whether you develop them, interact with them, debug them, etc. I'm not advocating for writing your entire web app client with bash. What I'm saying is that being able to quickly fire off an http request from the terminal is a very valuable skill that can a lot of time.
Linux is mostly underrated by people who only use Windows. Linux and Mac offer a similar Unix-based terminal command line interface.
How can I save the output from the POST request? So for example I had to make a POST request with credentials and I get back a token. I want to store that token as I need it to make other API requests? Is there a way to store it in a variable?
First of all its a very useful video.
Could you also show how to use curl to download file from any website?
Thanks. To download a file you either need to redirect the output into a file or specify an output file with -o. So you either do "curl -o foo.jpg somehost.com/foo.jpg" or you do "curl somehost.com/foo.jpg > foo.jpg". Both will download into a local file foo.jpg.
How did you get into vim like that?
❤️
@kubucation no more new videos? :(
man this really help me.bettet than books rich dad poor dad by robert kyosaki
nice
#Learn y doing