To learn more about networking fundamentals check out my udemy course Fundamentals of Networking for Effective Backends Head to network.husseinnasser.com for a discount coupon
Hussein, I have a very very hard backend question for you. Ready? Here it is: Why is there a slash between HTTP and its version number? (e.g. HTTP/1.1, HTTP/2, HTTP/3)
There's no special meaning. It is just a convention; in HTTP, we make requests with the help of URLs. They use "/" just to say that you are still using HTTP but another version(path), e.g youtube.com/watch and ruclips.net/user/shorts
To learn more about networking fundamentals check out my udemy course Fundamentals of Networking for Effective Backends Head to network.husseinnasser.com for a discount coupon
Your passion for backend tech is contagious and I deeply appreciate that.
Out-of-the-box content! As always, again a great job :-)
Always a pleasure to watch this kind of content, it’s pretty cool
My mom agrees that you speaking about this topic sound like sage exploring the arcane secrets of RFCs and eccentric protocols.
Best in-depth explanation!
A silly fact, an industry term which applies is: Flash Of Unstyled Text aka FOUT
And the word fout in Dutch means wrong.
Hussein, I have a very very hard backend question for you. Ready? Here it is:
Why is there a slash between HTTP and its version number? (e.g. HTTP/1.1, HTTP/2, HTTP/3)
I genuinely don’t know the answer 😅
There's no special meaning. It is just a convention; in HTTP, we make requests with the help of URLs. They use "/" just to say that you are still using HTTP but another version(path), e.g youtube.com/watch and ruclips.net/user/shorts
Thnx 🙂
this content is always an amazing #amflearningbydoing #amflearning