| ||
Mon 2024-12-02
Threads Won't Take You South of Market Sat 2024-11-30
Fri 2024-11-29
Wed 2024-11-27
Tue 2024-11-26
Sat 2024-11-23
Musk brigading government employees Thu 2024-11-21
Wed 2024-11-20
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
HTTP 1.1 has a dizzying array of
response
codes. These are important. Designing APIs for the success case is
easy; designing APIs for all the kinds of failures that can happen is
hard. Mark has some excellent
guidelines for aggregators handling various response codes.
100 101
I'm going to try 410 Gone to tell the spider to
buzz off;
that's stronger language than 404 and implies that the client
should not try that URL again. But 410 Gone is not a
HTTP/1.0 feature and the spider may not know HTTP/1.1, so it's
possible I'm now out of spec. Isn't versioning distributed systems fun?
200 201 202 203 204 205 206 300 301 302 303 304 305 306 307 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 500 501 502 503 504 505 |
|
