Author Topic: HTTP status codes illustrated with cycle facilities  (Read 9957 times)

Kim

  • Timelord
HTTP status codes illustrated with cycle facilities
« on: March 28, 2016, 12:59:18 am »
This occurred to me earlier, inspired by jo's percentage road sign stickerbook, the excellent HTTP Status Cats, and the DFT's Draft cycling and walking investment strategy.  I reckon that the combined efforts of YACF should be able to illustrate this complex technical subject through situations that any cyclist can understand.

For the benefit of non-geeks: HTTP status codes are short numerical codes used by web servers to communicate the result of a given request to a browser.  We're probably all familiar with '404' for "not found", but there are actually dozens of them (some more obscure than others).  There's a list of them - with descriptions of what they're used for - here.

So, what have you got?  I'll start us off in a second...
To ride the Windcheetah, first, you must embrace the cantilever...

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #1 on: March 28, 2016, 01:02:33 am »
401: Unauthorized
"Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided."



Illustrated by barakta OTP, defeated by a RADAR gate with a broken lock.
To ride the Windcheetah, first, you must embrace the cantilever...

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #2 on: March 28, 2016, 01:18:51 am »
100: Continue
"The server has received the request headers and that the client should proceed to send the request body."



Sustrans milepost on NCN8 at the Bryn-y-Fedwen summit.
To ride the Windcheetah, first, you must embrace the cantilever...

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #3 on: March 28, 2016, 01:34:44 am »
308: Permanent Redirect
"The request and all future requests should be repeated using another URI."



Former cycle parking at Birmingham New Street Station.
To ride the Windcheetah, first, you must embrace the cantilever...

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #4 on: March 28, 2016, 01:39:35 am »
424: Failed Dependency
"The request failed due to failure of a previous request."



Cycle parking at Asda Morrison's Five Ways.
To ride the Windcheetah, first, you must embrace the cantilever...

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #5 on: March 28, 2016, 01:42:40 am »
426: Upgrade Required
"The client should switch to a different protocol..."



Brompton failing to cope with the COR on Sponds Hill.
To ride the Windcheetah, first, you must embrace the cantilever...

T42

  • Tea tank
Re: HTTP status codes illustrated with cycle facilities
« Reply #6 on: March 28, 2016, 09:22:12 am »
307 Temporary Redirect (since HTTP/1.1)


I've dusted all those old bottles and set them up straight.

Re: HTTP status codes illustrated with cycle facilities
« Reply #7 on: March 28, 2016, 09:47:47 am »
101 Switching Protocols
"The requester has asked the server to switch protocols and the server has agreed to do so."



NCR 8 near Corris

Re: HTTP status codes illustrated with cycle facilities
« Reply #8 on: March 28, 2016, 10:46:59 am »
And how would you illustrate the only one that non-IT specialists know very well, I mean the 404?

mattc

  • n.b. have grown beard since photo taken
    • Didcot Audaxes
Re: HTTP status codes illustrated with cycle facilities
« Reply #9 on: March 28, 2016, 11:35:49 am »
Cycle-path Not Found?

Happened to me many many times. But hard to take a good photo of something ... that you couldnt find!


(In fact, this is probably the single thing that first put me off Sustrans routes, even before I started smashing up limbs and bike parts on them).

[Good work Kim. ]
Has never ridden RAAM
---------
No.11  Because of the great host of those who dislike the least appearance of "swank " when they travel the roads and lanes. - From Kuklos' 39 Articles

Re: HTTP status codes illustrated with cycle facilities
« Reply #10 on: March 28, 2016, 11:50:39 am »
Cycle-path Not Found?

Happened to me many many times. But hard to take a good photo of something ... that you couldnt find!

I've got these two satellite views of NCR 5 from some route-planning earlier this year...




T42

  • Tea tank
Re: HTTP status codes illustrated with cycle facilities
« Reply #11 on: March 28, 2016, 01:28:48 pm »
And how would you illustrate the only one that non-IT specialists know very well, I mean the 404?

Resource not found? Like this?



How not to leave Béziers.  The satellite view is Google Earth, the red track is what my Garmin recorded.
I've dusted all those old bottles and set them up straight.

Re: HTTP status codes illustrated with cycle facilities
« Reply #12 on: March 28, 2016, 06:01:33 pm »
(Seriously off topic, but I can't resist, please excuse me!)

How not to leave Béziers.  The satellite view is Google Earth, the red track is what my Garmin recorded.

That's very funny! I would expect the mayor of Béziers* to do whatever he can do to make sure that all those bl**dy strangers get out of his town as quickly as possible :demon:



*: the mayor is a member of the Front National

Re: HTTP status codes illustrated with cycle facilities
« Reply #13 on: March 28, 2016, 06:16:29 pm »
(Seriously off topic, but I can't resist, please excuse me!)

How not to leave Béziers.  The satellite view is Google Earth, the red track is what my Garmin recorded.

That's very funny! I would expect the mayor of Béziers* to do whatever he can do to make sure that all those bl**dy strangers get out of his town as quickly as possible :demon:



*: the mayor is a member of the Front National
Does the mayor only approve of triangles?  :facepalm:

Re: HTTP status codes illustrated with cycle facilities
« Reply #14 on: March 29, 2016, 05:39:52 am »
Does the mayor only approve of triangles?  :facepalm:

triangles?  ???


T42

  • Tea tank
Re: HTTP status codes illustrated with cycle facilities
« Reply #16 on: March 29, 2016, 09:10:03 am »
Our experience was more like the Bermuda Triangle.
I've dusted all those old bottles and set them up straight.


Mr Larrington

  • A bit ov a lyv wyr by slof standirds
  • Custard Wallah
    • Mr Larrington's Automatic Diary
Re: HTTP status codes illustrated with cycle facilities
« Reply #18 on: March 29, 2016, 01:23:57 pm »
Other mayors of other French towns are available, y'know ;)
External Transparent Wall Inspection Operative & Mayor of Mortagne-au-Perche
Satisfying the Bloodlust of the Masses in Peacetime

T42

  • Tea tank
Re: HTTP status codes illustrated with cycle facilities
« Reply #19 on: March 29, 2016, 02:56:04 pm »
Didn't notice any pistes cyclables in the Perche.

Meanwhile, here's 426 Upgrade Required.



(That was taken 5 years ago and it still is.)
I've dusted all those old bottles and set them up straight.

Vince

  • Can't climb; won't climb
Re: HTTP status codes illustrated with cycle facilities
« Reply #20 on: March 29, 2016, 06:44:35 pm »

450 Blocked by Windows Parental Controls
216km from Marsh Gibbon

mattc

  • n.b. have grown beard since photo taken
    • Didcot Audaxes
Re: HTTP status codes illustrated with cycle facilities
« Reply #21 on: March 29, 2016, 07:04:16 pm »
^Wins the Too Clever by 'Alf award.
Has never ridden RAAM
---------
No.11  Because of the great host of those who dislike the least appearance of "swank " when they travel the roads and lanes. - From Kuklos' 39 Articles

Re: HTTP status codes illustrated with cycle facilities
« Reply #22 on: March 29, 2016, 09:27:32 pm »
Didn't notice any pistes cyclables in the Perche.

It seems that the people who plan cycle paths believe that bicycles can only be ridden on perfectly flat ground. Sorry for the mayor of Mortagne-au-Perche, your town is not accessible to cyclists. (except for 5000 of them, once every 4 years)

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #23 on: March 29, 2016, 11:07:41 pm »
502: Bad Gateway
"The server was acting as a gateway or proxy and received an invalid response from the upstream server."



One of Sustrans' finest, somewhere in the vicinity of Bristol.
To ride the Windcheetah, first, you must embrace the cantilever...

Kim

  • Timelord
Re: HTTP status codes illustrated with cycle facilities
« Reply #24 on: March 29, 2016, 11:09:43 pm »
431: Request Header Fields Too Large
"The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large."



Bollards.
To ride the Windcheetah, first, you must embrace the cantilever...