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

hellymedic

  • Just do it!
Re: HTTP status codes illustrated with cycle facilities
« Reply #50 on: April 13, 2016, 08:46:39 pm »
And how would you illustrate the only one that non-IT specialists know very well, I mean the 404?

Like this, from HK's Facebook feed today...

Re: HTTP status codes illustrated with cycle facilities
« Reply #51 on: October 21, 2016, 03:05:09 pm »
415 - Unsupported Media Type



This was in the cycle cage at work. Chaq'un a son perch.

spesh

  • Keep calm and - Iä! Iä! Cthulhu fhtagn!
Re: HTTP status codes illustrated with cycle facilities
« Reply #52 on: October 21, 2016, 05:28:45 pm »
Top thread!  ;D :thumbsup:
This is not The Greatest Sig Line in the World, no.
This is just a tribute.

Arellcat

  • Velonautte
Re: HTTP status codes illustrated with cycle facilities
« Reply #53 on: October 24, 2016, 08:49:58 pm »
201: Created
"The request has been fulfilled, resulting in the creation of a new resource."


Arellcat

  • Velonautte
Re: HTTP status codes illustrated with cycle facilities
« Reply #54 on: October 24, 2016, 08:54:07 pm »
405: Method Not Allowed
"A request method is not supported for the requested resource…"


Re: HTTP status codes illustrated with cycle facilities
« Reply #55 on: October 24, 2016, 09:10:14 pm »
424 failed dependency


Mrs Pingu

  • Who ate all the pies? Me
    • Twitter
Re: HTTP status codes illustrated with cycle facilities
« Reply #56 on: December 07, 2016, 10:01:41 pm »
405: Method Not Allowed
"A request method is not supported for the requested resource…"



But what if there are 2 of you?
Do not clench. It only makes it worse.