20.02.2007 ~ HTTP 1.1 400
« May 2012 »
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31Tags
- .50
- 02
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 80s
- aircraft
- airsoft
- amiga
- amusing
- ArmA
- army
- arse
- babylon5
- backpage
- battlestar
- bebo
- caprica
- casa
- cat
- chinaDoll
- ciws
- clonmel
- code
- coen
- college
- computers
- cti
- custom
- Damn useful
- dev
- dez
- disappointing
- dublin
- fecking
- ffs
- frontpages
- funny
- gallery
- games
- google 12
- graffitti
- guard
- guns
- handy
- history
- I_don't_like_u
- iPad
- iPhone
- jfk
- karma
- landrover
- life
- lost
- love
- madonna/whore
- maritime
- meteor
- microsoft
- military
- mkiscript
- movie
- movies
- musing
- narc
- oh_its_you
- oldDaze
- pach
- pegasus
- phishing
- phone
- piltown
- podcasting
- police
- pussy
- quote
- rant
- religion
- retro
- right/wrong
- RIP
- Schrodinger
- ships
- simpsons
- sms
- software
- something
- song
- southpark
- spam
- spoiler
- struggle
- time_and_tide
- tv
- twilight
- ui
- unusual
- war
- weapon
- web2.0
- webdev
- weird
- what
- who
- windows
- women
- work
- wow
- writing
- xda
I came across a HTTP 400 error today while attempting to visit a site that was suffering the digg effect. I blushed. I blushed because it was my very first time. Knowing the 400 series of responses from the hypertext transfer protocol covers client specific errors, I checked if I sending any strange headers? Nope - nothing unusual there. Hmmmm!
Furrow browed, I had a quick gander at the W3C HTTP/1.1 RFC - the 400 error code is returned for a 'Bad Request'. I apologised and hit reload. Same error. I hit reload again... same error. I hit reload lots...
The site eventually loads. I wonder why I'd bothered hitting reload so many times. As I hit the back button I reflected that soon the name of the site will be lost to me, filed under miscellaneous and eventually forgotten. But my experience there will live on. It was after all, my very first time...
Anyway - the list of HTTP/1.1 response codes:
- 100 Continue
- 200 OK
- 201 Created
- 202 Accepted
- 204 No Content
- 205 Reset Content
- 206 Partial Content
- 300 Multiple Choices
- 301 Moved Permanently
- 302 Found
- 303 See Other
- 304 Not Modified
- 305 Use Proxy
- 306 (Unused)
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Request Entity Too Large
- 414 Request-URI Too Long
- 415 Unsupported Media Type
- 416 Requested Range Not Satisfiable
- 417 Expectation Failed
- 500 Internal Server Error
- 501 Not Implemented
- 502 Bad Gateway
- 503 Service Unavailable
- 504 Gateway Timeout
- 505 HTTP Version Not Supported
(Note to reader: I'm having one of those daze...)