
Things I Brushed Up On This Week
The HTTP Request Lifecycle
I have been interviewing for jobs recently, and as most devs know...
For further actions, you may consider blocking this person and/or reporting abuse
It's overall a great article but I have just one issue with it. In the teardown section you have written "Once the response has been fully delivered, the client sends a FIN packet at the TCP level, to which the server responds with an ACK" whereas the process should be the other way around. The server sends the FIN packet because it has no more packets to send and/or wants to close the connection and then the client responds with a FIN-ACK packet. Then the client sends it's own FIN packet and the server responsds with a FIN-ACK.
Daniel, this is a great post and a good refresher on the topic.
I ended up writing my own guide for HTTP connection lifecycle:
github.com/hardikvasa/http-connect...
It's kind of little-known secret that you can use gifs for the cover image :)
:D Beginners luck!
By the way, this is great timing. I was just looking to brush up on these topics myself.
I'm doing RegExes next!
This was great, Daniel! Thanks for taking the time to share what youβve learnt (or recently re-learnt, as the case my be). Iβm currently going through the same job-hunting process, so itβs great to have such ready refreshers on these topics!
Hey Daniel. This is a great article. I was asked this question in a recent interview for an Angular Dev job. I must say, I just mumbled about HTTP and secure handshake etc. Yes. I fluffed it, but thanks to your article, I wonβt make the same mistake.
However, having my own Windows Server 2012R2 VPS, I have encountered another protocol that I am sure is involved somehow. TLS. How does TLS fit into all this? I think we are on TLS1.2, currently...
This is really cool :) Waiting for more posts like this!
Glad you enjoyed it :D
Great write up!! I hope you continue your series. It is very valuable for devs to grok the underlying mechanisms, but all too often they are very little-known.
Thanks for reading it, working on more!
Really helpful article, Thank you
Crisp and Easy to understand! I appreciate your efforts to write this.
Great Job Daniel. Very elaborative and definitely worth sharing with my junior developers as well.
Great article!
Thank you, Daniel.
Thanks for taking the time to read!
I like that,
Thanks for sharing!
Thank you, glad you enjoyed it!
Very helpful article. Thank you!