Mirrors/httpstatuses
1
0
Fork 0
mirror of https://github.com/rmaake1/httpstatuses.git synced 2024-10-04 15:17:23 +02:00
Code Issues Packages Projects Releases Wiki Activity

3xx

Browse Source
This commit is contained in:
Samuel Ryan 2012-08-12 00:16:12 +01:00
parent c9297b1c57
commit 4fdaaa7201
4 changed files with 452 additions and 264 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.markdown
View File

@ -54,9 +54,10 @@ via git)
}
```
JSON should be formatted as above (lots of indentation :-)) using three space
tab and \r\n for new lines in descriptions. There's a good JSON formatter +
validator [here (use default options)](http://jsonformatter.curiousconcept.com/)
JSON should be formatted as above using four space tab and \r\n for new lines in
descriptions. There is no validation on the output and the only processing is
turning new lines into linebreaks, if you wish to include HTML that's fine
(preferably only links though and code tags)
## to do
clean up the HTML and CSS

160
codes/1.json
View File

@ -1,89 +1,89 @@
{
"class":{
"title":"Informational",
"class":"1"
},
"codes":{
"100":{
"code":"100",
"title":"Continue",
"summary":"Client should continue with request",
"descriptions":{
"wikipedia":{
"body":"This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#100"
"class":{
"title":"Informational",
"class":"1"
},
"codes":{
"100":{
"code":"100",
"title":"Continue",
"summary":"Client should continue with request",
"descriptions":{
"wikipedia":{
"body":"This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#100"
},
"ietf":{
"body":"The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":continue"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":continue"
}
}
},
"101":{
"code":"101",
"title":"Switching Protocols",
"summary":"Server is switching protocols",
"descriptions":{
"wikipedia":{
"body":"This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#101"
},
"101":{
"code":"101",
"title":"Switching Protocols",
"summary":"Server is switching protocols",
"descriptions":{
"wikipedia":{
"body":"This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#101"
},
"ietf":{
"body":"The server understands and is willing to comply with the client's request, via the Upgrade message header field, for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. \r\nThe protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The server understands and is willing to comply with the client's request, via the Upgrade message header field, for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. \r\nThe protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":switching_protocols"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":switching_protocols"
}
}
},
"102":{
"code":"102",
"title":"Processing (WebDAV) (RFC 2518)",
"summary":"Server has received and is processing the request",
"descriptions":{
"wikipedia":{
"body":"As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#102"
},
"102":{
"code":"102",
"title":"Processing (WebDAV) (RFC 2518)",
"summary":"Server has received and is processing the request",
"descriptions":{
"wikipedia":{
"body":"As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#102"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":processing"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":processing"
}
}
},
"103":{
"code":"103",
"title":"Checkpoint",
"summary":"resume aborted PUT or POST requests",
"descriptions":{
"wikipedia":{
"body":"This code is used in the Resumable HTTP Requests Proposal to resume aborted PUT or POST requests.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#103"
},
"103":{
"code":"103",
"title":"Checkpoint",
"summary":"resume aborted PUT or POST requests",
"descriptions":{
"wikipedia":{
"body":"This code is used in the Resumable HTTP Requests Proposal to resume aborted PUT or POST requests.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#103"
}
}
}
},
"122":{
"code":"122",
"title":"Request-URI too long",
"summary":"URI is longer than a maximum of 2083 characters",
"descriptions":{
"wikipedia":{
"body":"This is a non-standard IE7-only code which means the URI is longer than a maximum of 2083 characters.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#122"
},
"122":{
"code":"122",
"title":"Request-URI too long",
"summary":"URI is longer than a maximum of 2083 characters",
"descriptions":{
"wikipedia":{
"body":"This is a non-standard IE7-only code which means the URI is longer than a maximum of 2083 characters.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#122"
}
}
}
}
}
}
}
}

362
codes/2.json
View File

@ -1,200 +1,200 @@
{
"class":{
"title":"Success",
"class":"2"
},
"codes":{
"200":{
"code":"200",
"title":"OK",
"summary":"standard response for successful HTTP requests",
"descriptions":{
"wikipedia":{
"body":"Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#200"
"class":{
"title":"Success",
"class":"2"
},
"codes":{
"200":{
"code":"200",
"title":"OK",
"summary":"standard response for successful HTTP requests",
"descriptions":{
"wikipedia":{
"body":"Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#200"
},
"ietf":{
"body":"The request has succeeded. The information returned with the response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action;",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The request has succeeded. The information returned with the response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action;",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":ok"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":ok"
}
}
},
"201":{
"code":"201",
"title":"Created",
"summary":"request has been fulfilled; new resource created",
"descriptions":{
"wikipedia":{
"body":"The request has been fulfilled and resulted in a new resource being created.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#201"
},
"201":{
"code":"201",
"title":"Created",
"summary":"request has been fulfilled; new resource created",
"descriptions":{
"wikipedia":{
"body":"The request has been fulfilled and resulted in a new resource being created.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#201"
},
"ietf":{
"body":"The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.\r\n A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.\r\n A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":created"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":created"
}
}
},
"202":{
"code":"202",
"title":"Accepted",
"summary":"request accepted, processing pending",
"descriptions":{
"wikipedia":{
"body":"The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.[2]",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#202"
},
"202":{
"code":"202",
"title":"Accepted",
"summary":"request accepted, processing pending",
"descriptions":{
"wikipedia":{
"body":"The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.[2]",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#202"
},
"ietf":{
"body":"The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this. \r\nThe 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this. \r\nThe 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":accepted"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":accepted"
}
}
},
"203":{
"code":"203",
"title":"Non-Authoritative Information (since HTTP\/1.1)",
"summary":"request processed, information may be from another source",
"descriptions":{
"wikipedia":{
"body":"The server successfully processed the request, but is returning information that may be from another source.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#203"
},
"203":{
"code":"203",
"title":"Non-Authoritative Information (since HTTP\/1.1)",
"summary":"request processed, information may be from another source",
"descriptions":{
"wikipedia":{
"body":"The server successfully processed the request, but is returning information that may be from another source.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#203"
},
"ietf":{
"body":"The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":non_authoritative_information"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":non_authoritative_information"
}
}
},
"204":{
"code":"204",
"title":"No Content",
"summary":"request processed, no content returned",
"descriptions":{
"wikipedia":{
"body":"The server successfully processed the request, but is not returning any content.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#204"
},
"204":{
"code":"204",
"title":"No Content",
"summary":"request processed, no content returned",
"descriptions":{
"wikipedia":{
"body":"The server successfully processed the request, but is not returning any content.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#204"
},
"ietf":{
"body":"The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.\r\nIf the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.\r\nThe 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.\r\nIf the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.\r\nThe 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":no_content"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":no_content"
}
}
},
"205":{
"code":"205",
"title":"Reset Content",
"summary":"request processed, no content returned, reset document view",
"descriptions":{
"wikipedia":{
"body":"The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#205"
},
"205":{
"code":"205",
"title":"Reset Content",
"summary":"request processed, no content returned, reset document view",
"descriptions":{
"wikipedia":{
"body":"The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#205"
},
"ietf":{
"body":"The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":reset_content"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":reset_content"
}
}
},
"206":{
"code":"206",
"title":"Partial Content",
"summary":"partial resource return due to request header",
"descriptions":{
"wikipedia":{
"body":"The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#206"
},
"206":{
"code":"206",
"title":"Partial Content",
"summary":"partial resource return due to request header",
"descriptions":{
"wikipedia":{
"body":"The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#206"
},
"ietf":{
"body":"The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field indicating the desired range, and MAY have included an If-Range header field to make the request conditional.\r\nThe response MUST include the following header fields:\r\nEither a Content-Range header field (section 14.16) indicating the range included with this response, or a multipart\/byteranges Content-Type including Content-Range fields for each part. If a Content-Length header field is present in the response, its value MUST match the actual number of OCTETs transmitted in the message-body.\r\nDate\r\nETag and\/or Content-Location, if the header would have been sent in a 200 response to the same request\r\nExpires, Cache-Control, and\/or Vary, if the field-value might differ from that sent in any previous response for the same variant\r\nIf the 206 response is the result of an If-Range request that used a strong cache validator, the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.\r\nA cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly.\r\nA cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"ietf":{
"body":"The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field indicating the desired range, and MAY have included an If-Range header field to make the request conditional.\r\nThe response MUST include the following header fields:\r\nEither a Content-Range header field (section 14.16) indicating the range included with this response, or a multipart\/byteranges Content-Type including Content-Range fields for each part. If a Content-Length header field is present in the response, its value MUST match the actual number of OCTETs transmitted in the message-body.\r\nDate\r\nETag and\/or Content-Location, if the header would have been sent in a 200 response to the same request\r\nExpires, Cache-Control, and\/or Vary, if the field-value might differ from that sent in any previous response for the same variant\r\nIf the 206 response is the result of an If-Range request that used a strong cache validator, the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.\r\nA cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly.\r\nA cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":partial_content"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":partial_content"
}
}
},
"207":{
"code":"207",
"title":"Multi-Status (WebDAV) (RFC 4918)",
"summary":"XMLl, can contain multiple separate responses",
"descriptions":{
"wikipedia":{
"body":"The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#207"
},
"207":{
"code":"207",
"title":"Multi-Status (WebDAV) (RFC 4918)",
"summary":"XMLl, can contain multiple separate responses",
"descriptions":{
"wikipedia":{
"body":"The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#207"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":multi_status"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":multi_status"
}
}
},
"208":{
"code":"208",
"title":"Already Reported (WebDAV) (RFC 5842)",
"summary":"results previously returned ",
"descriptions":{
"wikipedia":{
"body":"The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#208"
},
"208":{
"code":"208",
"title":"Already Reported (WebDAV) (RFC 5842)",
"summary":"results previously returned ",
"descriptions":{
"wikipedia":{
"body":"The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#208"
}
}
}
},
"226":{
"code":"226",
"title":"IM Used (RFC 3229)",
"summary":"request fulfilled, reponse is instance-manipulations",
"descriptions":{
"wikipedia":{
"body":"The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#226"
},
"226":{
"code":"226",
"title":"IM Used (RFC 3229)",
"summary":"request fulfilled, reponse is instance-manipulations",
"descriptions":{
"wikipedia":{
"body":"The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#226"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":im_used"
}
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":im_used"
}
}
}
}
}
}
}

187
codes/3.json
View File

@ -0,0 +1,187 @@
{
"class":{
"title":"Redirection",
"class":"3"
},
"codes":{
"300":{
"code":"300",
"title":"Multiple Choices",
"summary":"multiple options for the resource delivered",
"descriptions":{
"wikipedia":{
"body":"Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#300"
},
"ietf":{
"body":"The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.\r\nUnless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content- Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.\r\nIf the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":multiple_choices"
}
}
},
"301":{
"code":"301",
"title":"Moved Permanently",
"summary":"this and all future requests directed to the given URI",
"descriptions":{
"wikipedia":{
"body":"This and all future requests should be directed to the given URI.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#301"
},
"ietf":{
"body":"The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.\r\nThe new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).\r\nIf the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.\r\nNote: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP\/1.0 user agents will erroneously change it into a GET request.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":moved_permanently"
}
}
},
"302":{
"code":"302",
"title":"Found",
"summary":"response to request found via alternative URI",
"descriptions":{
"wikipedia":{
"body":"This is an example of industrial practice contradicting the standard. HTTP\/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was \"Moved Temporarily\"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP\/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, some Web applications and frameworks use the 302 status code as if it were the 303.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#302"
},
"ietf":{
"body":"The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.\r\nThe temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).\r\nIf the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.\r\nNote: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":found"
}
}
},
"303":{
"code":"303",
"title":"See Other",
"summary":"response to request found via alternative URI",
"descriptions":{
"wikipedia":{
"body":"The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT\/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#303"
},
"ietf":{
"body":"The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.\r\nThe different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).\r\nNote: Many pre-HTTP\/1.1 user agents do not understand the 303 status. When interoperability with such clients is a concern, the 302 status code may be used instead, since most user agents react to a 302 response as described here for 303.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":see_other"
}
}
},
"304":{
"code":"304",
"title":"Not Modified",
"summary":"resource has not been modified since last requested",
"descriptions":{
"wikipedia":{
"body":"Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#304"
},
"ietf":{
"body":"If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.\r\nThe response MUST include the following header fields:\r\nDate, unless its omission is required\r\nIf a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by RFC 2068), caches will operate correctly.\r\nETag and\/or Content-Location, if the header would have been sent in a 200 response to the same request\r\nExpires, Cache-Control, and\/or Vary, if the field-value might differ from that sent in any previous response for the same variant\r\nIf the conditional GET used a strong cache validator, the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.\r\nIf a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.\r\nIf a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":not_modified"
}
}
},
"305":{
"code":"305",
"title":"Use Proxy (since HTTP\/1.1)",
"summary":"content located elsewhere, retrieve from there",
"descriptions":{
"wikipedia":{
"body":"Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#305"
},
"ietf":{
"body":"The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.\r\nNote: RFC 2068 was not clear that 305 was intended to redirect a single request, and to be generated by origin servers only. Not observing these limitations has significant security consequences.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":use_proxy"
}
}
},
"306":{
"code":"306",
"title":"Switch Proxy",
"summary":"subsequent requests should use the specified proxy",
"descriptions":{
"wikipedia":{
"body":"No longer used. Originally meant \"Subsequent requests should use the specified proxy.\"",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#306"
},
"ietf":{
"body":"The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
}
},
"307":{
"code":"307",
"title":"Temporary Redirect (since HTTP\/1.1)",
"summary":"connect again to different uri as provided",
"descriptions":{
"wikipedia":{
"body":"In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#307"
},
"ietf":{
"body":"The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.\r\nThe temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP\/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.\r\nIf the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.",
"link":"http:\/\/www.ietf.org\/rfc\/rfc2616.txt"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":temporary_redirect"
}
}
},
"308":{
"code":"308",
"title":"Resume Incomplete",
"summary":"resumable HTTP Requests",
"descriptions":{
"wikipedia":{
"body":"This code is used in the Resumable HTTP Requests Proposal to resume aborted PUT or POST requests.",
"link":"http:\/\/en.wikipedia.org\/wiki\/List_of_HTTP_status_codes#308"
}
},
"references":{
"rails":{
"title":"Rails HTTP Status Symbol",
"value":":no_content"
}
}
}
}
}