Hello, nice video. But some corrections / constructive critisism. HTTP is stateless, but not connectionless as you say in the video. HTTP uses TCP for the underlying connection: "Transport Layer: TCP is a connection-oriented transport protocol. UDP is connectionless." So actually the client does NOT disconnect after it has sent the request, it will keep the connection open until it receives the response, then it disconnects. No state is kept for this HTTP transaction, this is why it is called stateless. Any new HTTP request will cause a new TCP connection. Of course this is a simplification, in the real world this would be very inefficient, so web servers make use of Keep-alives to enable reusing the same TCP connection for multiple requests.
"At the application layer, HTTP is connectionless. However, HTTP requires a connection oriented service to operate, and that is where TCP comes into play". In other words you can't just say wether its connection less or connection oriented without further explanation of your statement. And basically both of them can be true, depending on the explanation.
With understanding of the OSI reference model, he isn't wrong. This is helpful for me as a beginner to make it less complicated. Obviously there is some connection on some level of the OSI model IP/TCP model.
OSI model is composed of 7 layers however the "TCP/IP" stack is composed of 5 layers. The OSI model it is a "standard" it is not meant to be built. it describes a standard. TCP/IP it was built by the OSI model standard... thought ;)
Hi Tech Cave, The technical explanation in the video are really clear and understandable just like a story and hence simplifying the process of the learning technical stuffs Just one request,can you please keep uploading more technical videos .It would be really helpful !!
this video more works for java script programmers than any body else does. specially in about 4:41 timeline you can see title of a java script program syntax. i.e i used java script as an application program for a while it's suggested by web-programmers
Almost Six years since I uploaded this video! I just want to say thank you for all of you! This makes me feel nostalgic. I couldn't focus solely on the channel during this time, but hopefully, I'll come back stronger this time. Support me by liking, sharing, and subscribing. Also you support the The TechCave via ko-fi.com/thetechcave
Thank you so much, this is the best explanation of how HTTP works, and I like the way you use the graphics to explain what you are talking about, simple, clear and concise.
Can you explain a little more specifically and detailed how the http message gets from your computer to the service and back? For instance, does you browser run methods that invoke your OS to send it to your modem which runs code to send it to some service center that then runs code to send it to the server and then repeats the process all the way back and read again by your browser? How are all these things authenticated? This is just my guess but I've never seen it explained in that type of detail
Thank you for the informative video. I have however a question regarding the connectionless nature of http as per your explanation. Since HTTP/S runs on top of TCP 80 / 443 which is a connection-oriented protocol, why then is HTTP considered connectionless?
You can dive deeper through detailed books like "Restful Web Services" by Richardson and Ruby. In terms of practice, side projects using public APIs or develop your own Complex API.
1:24 ? wtf no- the client stays connected until the server has the response ready and then it connects and sends it the response and only after its sent the response from the server does it disconnect .. it is re-established again for the next request (at least in http1.1, http2.0 is different)
you have a little mistake. the request and response happens in the same connection the client:- 1- open a connection to server 2- send request The server:- 1- accept connection 2-accept request 3- send response 4- close the connection
Sounds so correct. This is what I always knew of until the video confused me actually. No such thing as connect-to-server, close, connect-to-client, close. It's only a connect-to-server, do things, send back response, close. Here: en.wikipedia.org/wiki/HTTP_persistent_connection
@The TechCave I must say that is a pretty good content to learn. However, I would like understand HTTP thoroughly. Could you please suggest a way to achieve this or even a book would do ? Thank you in adavance.
Hello, nice video. But some corrections / constructive critisism. HTTP is stateless, but not connectionless as you say in the video. HTTP uses TCP for the underlying connection:
"Transport Layer: TCP is a connection-oriented transport protocol. UDP is connectionless."
So actually the client does NOT disconnect after it has sent the request, it will keep the connection open until it receives the response, then it disconnects. No state is kept for this HTTP transaction, this is why it is called stateless. Any new HTTP request will cause a new TCP connection.
Of course this is a simplification, in the real world this would be very inefficient, so web servers make use of Keep-alives to enable reusing the same TCP connection for multiple requests.
In this video I tried to talk just in the application layer. thanks for the clarification ^^
"At the application layer, HTTP is connectionless. However, HTTP requires a connection oriented service to operate, and that is where TCP comes into play". In other words you can't just say wether its connection less or connection oriented without further explanation of your statement. And basically both of them can be true, depending on the explanation.
With understanding of the OSI reference model, he isn't wrong. This is helpful for me as a beginner to make it less complicated. Obviously there is some connection on some level of the OSI model IP/TCP model.
OSI model is composed of 7 layers however the "TCP/IP" stack is composed of 5 layers. The OSI model it is a "standard" it is not meant to be built. it describes a standard. TCP/IP it was built by the OSI model standard... thought ;)
👍
I've been reading about HTTP headers and it wasn't clicking for me. Found this video and it all makes sense now! Thank you so much!
this explanation was the most usefull one for me! thanks!
Really impressive.....the way you divided the whole tutorial..thats amazing and at the the summary...MAY GOD SHOWER YOU WITH MORE KNOWLEDGE
This is a crystal clear explanation for beginners like me
Best video ever to explain HTTP protocol. Thanks.
Great video. one suggestion: try using a bright text color when using a dark background. thanks for the clear and simple explanation
Hi Tech Cave,
The technical explanation in the video are really clear and understandable just like a story and hence simplifying the process of the learning technical stuffs
Just one request,can you please keep uploading more technical videos .It would be really helpful !!
Every educational video should be like this: concise and insightful. It is difficult to find videos like this.
fantastic explanation! concise yet thorough enough, and most importantly, clearly presented. thank you very much
To understand how this things works is just think about a client/waiter/cooker relationship. All of them apply the same concept.
Cook, not cooker
True, like an AutoMac
1:18 - Three important things about the http protocol
very nice explanation, many thanks dude.
Thank you so much indeed sir. It is real helpful lessons for me.
2023 still awesome!
You really ought to consider a Patreon. You've got great content.
You have created a clear immage of http. Thanks Sir.
this video begins at 0:33
Great video! Thank you so much!
Nice Video! i finally understood how and why Request and Response works Thank You :)
Thank you, good explanation of what HTTP is!
WebDev Cave , Keep Creating videos. Your videos are just superb. Subscribed you
Great resource to learn about HTTP. Thanks for posting
Simple and clear, very good. Thank you.
You mentioned there are some good books out there on this topic. Can you suggest some?
hey thank you for the video!!, it is very summed up and it works for a brush up for networking purposes, hope that you get more like later on!!
You're Welcome!
this video more works for java script programmers than any body else does. specially in about 4:41 timeline you can see title of a java script program syntax. i.e i used java script as an application program for a while it's suggested by web-programmers
thank you so much for the explanation in the easiest way! this video is so much helpful for me!
Almost Six years since I uploaded this video! I just want to say thank you for all of you! This makes me feel nostalgic. I couldn't focus solely on the channel during this time, but hopefully, I'll come back stronger this time. Support me by liking, sharing, and subscribing. Also you support the The TechCave via ko-fi.com/thetechcave
My professor linked your video in his course at university :D
Which book is best?
This video is extremely helpful!! Thank you!
Wow, your content is great !! Thank you so much dude ^^
Felt very comprehensive. Thanks !
Your videos are so great. Hope you make more.
Underrated channel dude. Thanks !
Great Video! To claify, HTTP is a format to send data via the internet to other computers. Is this a good way to summarize it?
Definitely learnt something here. Thanks a lot!!!
brother please make some videos on cookies also . i want to understand them
everything aside, your voice is on another level. I don't know but I am in love with it!
Excellent tutorial. Thanks a lot.
Informative.
Thank you so much, this is the best explanation of how HTTP works, and I like the way you use the graphics to explain what you are talking about, simple, clear and concise.
Hands Down! Best One
Just amazing video on HTTP :)
Thanks for the video simple and straightforward
Can you explain a little more specifically and detailed how the http message gets from your computer to the service and back? For instance, does you browser run methods that invoke your OS to send it to your modem which runs code to send it to some service center that then runs code to send it to the server and then repeats the process all the way back and read again by your browser? How are all these things authenticated? This is just my guess but I've never seen it explained in that type of detail
Amazing upload more and more vedio good way of teaching .
God bless you .
Keep it up,
From Pakistan 🇵🇰
Super delivery of message nice and thank you
The middle box in the "user case" at 7:41 has been copy/pasted from the request's user case. eg "Host" is not a header parameter in the response.
thank you for the explanation !
Thank you for this video! very helpful!
Thank you. This video is awesome and so simplified :)
مشكوووور علي الفيديو اخ ايوب . ياريت لو تنزل فيدوهات اكتر
Hey! Thanks Yusuf! New videos will be uploaded soon. Stay Tuned! ;)
finally a video that explains this well, thx
this is such a great explanation
Thank you!
Clear and concise, thanks
I love finding new accents and stuff, so, out of curiosity, what part of the world are you from?
Morocco :)
@@TheTechCave That's very cool thanks :)
Thank you for the informative video. I have however a question regarding the connectionless nature of http as per your explanation. Since HTTP/S runs on top of TCP 80 / 443 which is a connection-oriented protocol, why then is HTTP considered connectionless?
the video is bullshit
Thankyou so much..got clear basic idea about this topic!
Thanks for such great knowledge
Hello, this video is very helpful, simple and easily understandable.
good and informative . providing free information is a nice job
Thanks! Very well explained
Thanks m8! A lot of concepts cleared out! :)
Thanks for making such a good video and sharing your knowledge
Thank you this video is so helpful !!!
Very well said Sir.
Thank you very much
Sound quality should be considered
I was going to POST an http joke, but you might not GET it
Wait. Isn't the URI in the Start Line of the HTTP Message actually a URN?
Http is stateless not connectionless. As it uses TCP it couldn’t be connectionless.
Nice explanation, thanks
very good....teaching skills
It was really helpful👍👍👍
man that's an amazing video.. so clearly explained by you, thank you!!
It was helpful. Thank you.
Very useful video. Thank you so much.
Awesome! Thank you very much!
Good explanation bro
Thanks for this. It's a great start to HTTP, but I'm looking for something a LOT more detailed with practice work. Do you have any suggestions?
You can dive deeper through detailed books like "Restful Web Services" by Richardson and Ruby. In terms of practice, side projects using public APIs or develop your own Complex API.
@@TheTechCave that's nice thanks for this info 🙂
SHERIFF IS THE HTTP all levels's and watching all ping and web internet all watching every thing
Well explained. Love it :)
Why this video doesn't have more views?
I want to see
Nice Video, good explanation
thanks, great content!
1:24 ? wtf no-
the client stays connected until the server has the response ready and then it connects and sends it the response and only after its sent the response from the server does it disconnect .. it is re-established again for the next request (at least in http1.1, http2.0 is different)
dang, this video's good, thanks for the info
2:12 anew? is it again?
A Big Thankyou SIR
This video has cleared all my doubts.
I am from INDIA.
♥️♥️♥️
really excellent video, cheers
Very informative video! thanks! :D
Well organized and explained tutorial
very clear thank you very much my friend
It is an excellent learning video. Thank you teacher for sharing your knowledge!
The same name, the same passion and maybe the same country hahaha keep it up bro :D
Yup! Your family name is common in my region!
very well explained thank you
very helpful ,thank you
you have a little mistake. the request and response happens in the same connection
the client:-
1- open a connection to server
2- send request
The server:-
1- accept connection
2-accept request
3- send response
4- close the connection
Sounds so correct. This is what I always knew of until the video confused me actually. No such thing as connect-to-server, close, connect-to-client, close. It's only a connect-to-server, do things, send back response, close. Here: en.wikipedia.org/wiki/HTTP_persistent_connection
@The TechCave I must say that is a pretty good content to learn. However, I would like understand HTTP thoroughly. Could you please suggest a way to achieve this or even a book would do ?
Thank you in adavance.