10 Common HTTP Statuses Explained With Pizza Gifs

Don't understand HTTP Statuses? Do 505's and 400's seem the same to you? Let me explain the differences between the top 10 most common HTTP statuses using some some amazing pizza metaphors via status.pizza.

200 OK

Via status.pizza

Technical Jargon: The request was successful. The information returned with the response is in the format you asked for. Everything is great and went as expected.

Pizza Jargon: We received and ate pizza. It was delicious.

404 Not Found

Via status.pizza

Technical Jargon: The server has not found anything matching the request. No indication is given of whether the condition is temporary or permanent.

Pizza Jargon: We have no idea where the pizza is. It's probably lost in space somewhere. Sorry.

500 Internal Server Error

Via status.pizza

Technical Jargon: The server encountered an unexpected condition which prevented it from fulfilling the request.

Pizza Jargon: Something really bad happen to the pizza. You asked for some pizza but the pizza chef couldn't make it in today - he might have died in a shark accident.

304 Not Modified

Via status.pizza

Technical Jargon: Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. This means that there is no need to retransmit the resource, since the client still has a cached copy.

Pizza Jargon: The pizza you already have from before is good to eat. No need to order new pizza.

401 Unauthorized

Via status.pizza

Technical Jargon: The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource.

Pizza Jargon: You are not allowed to eat this pizza. Sorry.

410 Gone

Via status.pizza

Technical Jargon: The requested resource is no longer available at the server and no forwarding address is known.

Pizza Jargon: There used to be some pizza here. Now there isn't. DEAL WITH IT.

301 Moved Permanently

Via status.pizza

Technical Jargon: The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs.

Pizza Jargon: This pizza has been permanently moved to a new location (by Beyonce).

413 Request Entity Too Large

Via status.pizza

Technical Jargon: The request is larger than the server is willing or able to process.

Pizza Jargon: The pizza that was made is WAY too big to deliver. Sorry.

508 Loop Detected

Technical Jargon: The server detected an infinite loop while processing the request

Pizza Jargon: Woah, what!

400 Bad Request

Via status.pizza

Technical Jargon: The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Pizza Jargon: It's not our fault that you wanted the pizza delivered to your roof.