From 13ccc059d05ab047b0ea0f32d202b0327bf40b08 Mon Sep 17 00:00:00 2001 From: Mukund Sivaraman Date: Sun, 13 Sep 2009 03:53:32 +0530 Subject: doc: Rename some files --- doc/HTTP_ERROR_CODES | 61 ------------------------------------------------ doc/Makefile.am | 4 ++-- doc/RFC_INFO | 23 ------------------ doc/http-error-codes.txt | 61 ++++++++++++++++++++++++++++++++++++++++++++++++ doc/http-rfcs.txt | 23 ++++++++++++++++++ 5 files changed, 86 insertions(+), 86 deletions(-) delete mode 100644 doc/HTTP_ERROR_CODES delete mode 100644 doc/RFC_INFO create mode 100644 doc/http-error-codes.txt create mode 100644 doc/http-rfcs.txt (limited to 'doc') diff --git a/doc/HTTP_ERROR_CODES b/doc/HTTP_ERROR_CODES deleted file mode 100644 index b7fb0cd..0000000 --- a/doc/HTTP_ERROR_CODES +++ /dev/null @@ -1,61 +0,0 @@ -The following is a list of the response codes for the various states of -the server. Currently I would recommend we stick to the HTTP/1.0 return -codes for our errors. Once we start to support the distinction between -HTTP/1.0 and HTTP/1.1 requests from the client, then we can use the -HTTP/1.1 responses. - -- rjkaes - -[ Taken from Apache: The Definitive Guide by Ben Laurie & Peter Laurie. - Published by O'Reilly & Associates, Inc. pg. 146-147 ] - -HTTP/1.0 -200 OK -302 Found -304 Not Modified -400 Bad Request -401 Unauthorized -403 Forbidden -404 Not Found -500 Server error -501 Not Implemented -502 Bad Gateway -503 Out of resources - -HTTP/1.1 -100 Continue -101 Switching Protocols -200 Ok -201 Created -202 Accepted -203 Non-Authoritative Information -204 No Content -205 Reset Content -206 Partial Content -300 Multiple Choices -301 Moved Permanently -302 Moved Temporarily -303 See Other -304 Not Modified -305 Use Proxy -400 Bad Request -401 Unauthorized -402 Payment Required -403 Forbidden -404 Not Found -405 Method Not Allowed -406 Not Acceptable -407 Proxy Authentication Required -408 Request Time-out -409 Conflict -410 Gone -411 Length Required -412 Precondition Failed -413 Request Entity Too Large -414 Request-URI Too Large -415 Unsupported Media Type -500 Internal Server Error -501 Not Implemented -502 Bad Gateway -503 Service Unavailable -504 Gateway Time-out -505 HTTP Version not supported diff --git a/doc/Makefile.am b/doc/Makefile.am index ade0939..b246228 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -4,7 +4,7 @@ SUBDIRS = \ EXTRA_DIST = \ tinyproxy.conf \ HTML_VARIABLES \ - HTTP_ERROR_CODES \ - RFC_INFO \ + http-error-codes.txt \ + http-rfcs.txt \ filter-howto.txt diff --git a/doc/RFC_INFO b/doc/RFC_INFO deleted file mode 100644 index 081d2d0..0000000 --- a/doc/RFC_INFO +++ /dev/null @@ -1,23 +0,0 @@ -INFO ----- -The following files were/are useful for the proper coding of -tinyproxy. Please note: someday tinyproxy will actually be RFC -compliant, but today is not that day. Right now tinyproxy is pretty -close to being HTTP/1.0 compliant, but there are probably a few -incompatibilities kicking around. - -RFCs ----- -1945 Hypertext Transfer Protocol -- HTTP/1.0 -2396 Uniform Resource Identifiers (URI): Generic Syntax -2616 Hypertext Transfer Protocol -- HTTP/1.1 -2617 HTTP Authentication: Basic and Digest Access Authentication - -POSSIBLE LOCATION ------------------ -There are many places to obtain a copy of the RFCs, but I use - - http://www.rfc-editor.org/ - -since it provides a great search feature for finding all the RFCs for -a particular topic. diff --git a/doc/http-error-codes.txt b/doc/http-error-codes.txt new file mode 100644 index 0000000..b7fb0cd --- /dev/null +++ b/doc/http-error-codes.txt @@ -0,0 +1,61 @@ +The following is a list of the response codes for the various states of +the server. Currently I would recommend we stick to the HTTP/1.0 return +codes for our errors. Once we start to support the distinction between +HTTP/1.0 and HTTP/1.1 requests from the client, then we can use the +HTTP/1.1 responses. + -- rjkaes + +[ Taken from Apache: The Definitive Guide by Ben Laurie & Peter Laurie. + Published by O'Reilly & Associates, Inc. pg. 146-147 ] + +HTTP/1.0 +200 OK +302 Found +304 Not Modified +400 Bad Request +401 Unauthorized +403 Forbidden +404 Not Found +500 Server error +501 Not Implemented +502 Bad Gateway +503 Out of resources + +HTTP/1.1 +100 Continue +101 Switching Protocols +200 Ok +201 Created +202 Accepted +203 Non-Authoritative Information +204 No Content +205 Reset Content +206 Partial Content +300 Multiple Choices +301 Moved Permanently +302 Moved Temporarily +303 See Other +304 Not Modified +305 Use Proxy +400 Bad Request +401 Unauthorized +402 Payment Required +403 Forbidden +404 Not Found +405 Method Not Allowed +406 Not Acceptable +407 Proxy Authentication Required +408 Request Time-out +409 Conflict +410 Gone +411 Length Required +412 Precondition Failed +413 Request Entity Too Large +414 Request-URI Too Large +415 Unsupported Media Type +500 Internal Server Error +501 Not Implemented +502 Bad Gateway +503 Service Unavailable +504 Gateway Time-out +505 HTTP Version not supported diff --git a/doc/http-rfcs.txt b/doc/http-rfcs.txt new file mode 100644 index 0000000..081d2d0 --- /dev/null +++ b/doc/http-rfcs.txt @@ -0,0 +1,23 @@ +INFO +---- +The following files were/are useful for the proper coding of +tinyproxy. Please note: someday tinyproxy will actually be RFC +compliant, but today is not that day. Right now tinyproxy is pretty +close to being HTTP/1.0 compliant, but there are probably a few +incompatibilities kicking around. + +RFCs +---- +1945 Hypertext Transfer Protocol -- HTTP/1.0 +2396 Uniform Resource Identifiers (URI): Generic Syntax +2616 Hypertext Transfer Protocol -- HTTP/1.1 +2617 HTTP Authentication: Basic and Digest Access Authentication + +POSSIBLE LOCATION +----------------- +There are many places to obtain a copy of the RFCs, but I use + + http://www.rfc-editor.org/ + +since it provides a great search feature for finding all the RFCs for +a particular topic. -- cgit v1.2.3