This week, we're wrapping up the September challenge with our final HTTP status code prompt.

Last week, the CodePen community got creative with 403 Forbidden. Check out our HTTP Status 403 collection to see the Pens from the challenge!

This Week's Status Code: 408 Request Timeout

As official and standardized as all these HTTP status codes seem, at the end of the day, it's really just some programmer somewhere like you or me who thinks "hmmmmm I guess I'll make this software respond with this code, makes sense to me".

This week's code, the 408 Request Timeout code, might drive that home a bit. 'The client did not produce a request within the time that the server was prepared to wait.' As in, the browser took to long to do something and the server grew tired of waiting and thus is erroring this particular response. In a sense, the opposite of a 504 error in which the server ('gateway') took too long. There are really no standards around timing out requests. Your servers and site can do almost whatever they like, although browsers do likely have some extreme edge-case caps.

September's Challenge Sponsor: Jamf

This month we have Jamf as a sponsor. Jamf Now allows you to manage all the Apple devices in your company. For example, remotely configuring all the settings on all of your iPad, iPhone and Mac devices quickly and consistently.

Your Challenge

Design an error page around the idea that something just took too dang long.

How to Participate

Create a Pen → and tag it codepenchallenge and the weekly tag cpc-408. We'll gather those Pens into a collection and share our favorites on Twitter and Instagram (Use the #CodePenChallenge tag on Twitter and Instagram as well).

Ideas

  1. Clocks! Watches! Timers! Progress bars! Demonstrating time has so many strong visual metaphors, you'll surely be able to find something that fits the bill.
  2. This error code gets at the delicate dance that browsers and servers are constantly engaged in. We see the browser, but the server is the hidden partner. Could your design showcase the server somehow?
  3. Another aspect to a 408 is that the client is welcome to re-try the request. Like the server isn't saying yes, but it isn't saying no. Rather coy isn't it?

Resources

  • If you're particularly interested in the nuts and bolts of a 408 error, here's a massive article from Andrew Powell-Morse.
  • This isn't specific to 408, but we haven't linked up httpstatuses.com yet, which is a rather cleanly designed reference site for all the codes.
  • If you're wanting to get fancy with the design of your error page, there are so many incredible design resources out there on the web. It's always fun and helpful to check out people's takes on rounding up the best ones. Here's a great one by Jessica Paoli.