-
-
Save ahmedfarooki/228845a6b52dfd3d0ce10f94f13a1f9b to your computer and use it in GitHub Desktop.
Revisions
-
tonypujals revised this gist
Dec 8, 2014 . 1 changed file with 2 additions and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -1,5 +1,6 @@ Reference: RFC 2616 - HTTP Status Code Definitions * [HTTP/1.1 Status Code Definitions](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html) * [Additional HTTP Status Codes](http://tools.ietf.org/html/rfc6585) ### General * 400 BAD REQUEST: The request was invalid or cannot be otherwise served. An accompanying error message will explain further. For security reasons, requests without authentication are considered invalid and will yield this response. -
tonypujals revised this gist
Dec 3, 2014 . 1 changed file with 1 addition and 0 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -24,4 +24,5 @@ Reference: RFC 2616 - HTTP Status Code Definitions * 202 ACCEPTED: The request has been accepted for further processing, which will be completed sometime later. ### HTTP DELETE * 202 ACCEPTED: The request has been accepted for further processing, which will be completed sometime later. * 204 OK: The request was successful; the resource was deleted. -
tonypujals renamed this gist
Dec 3, 2014 . 1 changed file with 0 additions and 0 deletions.There are no files selected for viewing
File renamed without changes. -
tonypujals created this gist
Dec 3, 2014 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,27 @@ Reference: RFC 2616 - HTTP Status Code Definitions * http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html ### General * 400 BAD REQUEST: The request was invalid or cannot be otherwise served. An accompanying error message will explain further. For security reasons, requests without authentication are considered invalid and will yield this response. * 401 UNAUTHORIZED: The authentication credentials are missing, or if supplied are not valid or not sufficient to access the resource. * 403 FORBIDDEN: The request has been refused. See the accompanying message for the specific reason (most likely for exceeding rate limit). * 404 NOT FOUND: The URI requested is invalid or the resource requested does not exists. * 406 NOT ACCEPTABLE: The request specified an invalid format. * 410 GONE: This resource is gone. Used to indicate that an API endpoint has been turned off. * 429 TOO MANY REQUESTS: Returned when a request cannot be served due to the application’s rate limit having been exhausted for the resource. * 500 INTERNAL SERVER ERROR: Something is horribly wrong. * 502 BAD GATEWAY: The service is down or being upgraded. Try again later. * 503 SERVICE UNAVAILABLE: The service is up, but overloaded with requests. Try again later. * 504 GATEWAY TIMEOUT: Servers are up, but the request couldn’t be serviced due to some failure within our stack. Try again later. ### HTTP GET * 200 OK: The request was successful and the response body contains the representation requested. * 302 FOUND: A common redirect response; you can GET the representation at the URI in the Location response header. * 304 NOT MODIFIED: There is no new data to return. ### HTTP POST or PUT * 201 OK: The request was successful, we updated the resource and the response body contains the representation. * 202 ACCEPTED: The request has been accepted for further processing, which will be completed sometime later. ### HTTP DELETE * 204 OK: The request was successful; the resource was deleted.