HTTP codes as Valentine’s Day comics
<p>With Valentine’s Day around the corner, it is a time for romantic hopefuls to ask out the object of their affection, and await an answer. It could be a simple “yes,” a sad “no,” or a cryptic “I don’t think about you that way, but maybe we can grab a coffee tomorrow?”</p>
<p>Which brings us to HTTP (Hypertext Transfer Protocol) codes . When a URL is typed in a browser, a request is sent out to the server and the browser awaits an answer, just like in our scenario. These answers come in the form of an HTTP code, which is a three-digit number that maps to an answer.</p>
<p>With the image of Valentine’s Day in mind, here are a few likely scenarios.</p>
<h1>200s: The Happy Ending</h1>
<p>Codes in the 200s generally mean that everything is OK. The request was received, understood, and there were no errors on the server. <a href="https://www.wsj.com/" rel="noopener ugc nofollow" target="_blank">This URL</a> will return a 200.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:289/1*kwO3FGPDyIXK_k4sWcObFw.png" style="height:356px; width:321px" /></p>
<p>The ideal ending for a browser + server, and a developer + their project</p>
<h1>300s: Redirect</h1>
<p>Codes in the 300s mean that the client must take further action to complete the request. The 300s are also where all redirects live.</p>
<p>A human will probably never see the 300 codes, as the browser is meant to seamlessly take the required action(s) without any user input. However, Search Engines will take these 300 codes seriously, so developers should take care to choose the correct code.</p>
<p><a href="https://medium.com/@hanilim/http-codes-as-valentines-day-comics-8c03c805faa0">Click Here</a></p>