From a1070953ff888850b6d9f2df1d94db4ac3583064 Mon Sep 17 00:00:00 2001 From: Jagadeesh Cheluvaraj Shetty Date: Thu, 22 Oct 2020 22:40:07 +0530 Subject: [PATCH 1/7] updated readme with http status code link. --- README.md | 4 +++- docs/images/http-status-code.md | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) create mode 100644 docs/images/http-status-code.md diff --git a/README.md b/README.md index 722c172..7668122 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,8 @@ +- [HTTP Status Codes](docs/http-status-code.md) + ## Run ### Install dependencies @@ -29,4 +31,4 @@ [JSON Schema - Getting started step by step](https://json-schema.org/learn/getting-started-step-by-step.html) [JSON Schema - Validator](https://jsonschemalint.com/#!/version/draft-07/markup/json) -**{ }** with ❤️ from [Jagadeesh C](https://www.linkedin.com/in/jagadeesh-c-2a3a9423) \ No newline at end of file +**{ }** with ❤️ from [Jagadeesh C](https://www.linkedin.com/in/jagadeesh-c-2a3a9423) diff --git a/docs/images/http-status-code.md b/docs/images/http-status-code.md new file mode 100644 index 0000000..5256e4c --- /dev/null +++ b/docs/images/http-status-code.md @@ -0,0 +1 @@ +# HTTP Status Codes From fda0a4b035d46732cf2698277c6adde0a93ec90a Mon Sep 17 00:00:00 2001 From: Jagadeesh Cheluvaraj Shetty Date: Thu, 22 Oct 2020 22:43:31 +0530 Subject: [PATCH 2/7] updated http status code link. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7668122..4a0ad0e 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ -- [HTTP Status Codes](docs/http-status-code.md) +- [HTTP Status Codes](https://github.com/jagadeeshshetty/rest-api-test-bdd/blob/doc/httpStatusCode/docs/images/http-status-code.md) ## Run From 7c820d36c0e397cd4330f720c951d58616ee64f5 Mon Sep 17 00:00:00 2001 From: Jagadeesh Cheluvaraj Shetty Date: Thu, 22 Oct 2020 22:58:37 +0530 Subject: [PATCH 3/7] update --- docs/images/http-status-code.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/images/http-status-code.md b/docs/images/http-status-code.md index 5256e4c..910c234 100644 --- a/docs/images/http-status-code.md +++ b/docs/images/http-status-code.md @@ -1 +1,15 @@ # HTTP Status Codes + +HTTP defines following these standard status codes that can be used to convey the results of a client’s request. + +The status codes are divided into the five categories. + +- `1xx: Informational` Communicates transfer protocol-level information. +- `2xx: Success` Indicates that the client’s request was accepted successfully. +- `3xx: Redirection` Indicates that the client must take some additional action in order to complete their request. +- `4xx: Client Error` This category of error status codes points the finger at clients. +- `5xx: Server Error` The server takes responsibility for these error status codes. + +## Reference + +[Restful API](https://restfulapi.net/http-status-codes/) From e6f5655977ff14d0ac9bb7626334ad1660bcd20a Mon Sep 17 00:00:00 2001 From: Jagadeesh Date: Fri, 23 Oct 2020 08:04:12 +0530 Subject: [PATCH 4/7] reformat --- docs/images/http-status-code.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/images/http-status-code.md b/docs/images/http-status-code.md index 910c234..014c923 100644 --- a/docs/images/http-status-code.md +++ b/docs/images/http-status-code.md @@ -4,11 +4,13 @@ HTTP defines following these standard status codes that can be used to convey th The status codes are divided into the five categories. -- `1xx: Informational` Communicates transfer protocol-level information. -- `2xx: Success` Indicates that the client’s request was accepted successfully. -- `3xx: Redirection` Indicates that the client must take some additional action in order to complete their request. -- `4xx: Client Error` This category of error status codes points the finger at clients. -- `5xx: Server Error` The server takes responsibility for these error status codes. +| Status code | Description | +| :------------------- | :--------------------------------------------------------------------------------------------- | +| `1xx: Informational` | Communicates transfer protocol-level information. | +| `2xx: Success` | Indicates that the client’s request was accepted successfully. | +| `3xx: Redirection` | Indicates that the client must take some additional action in order to complete their request. | +| `4xx: Client Error` | This category of error status codes points the finger at clients. | +| `5xx: Server Error` | The server takes responsibility for these error status codes. | ## Reference From 448f46834b618ecccdd5dfb6950c24344dc66ced Mon Sep 17 00:00:00 2001 From: Jagadeesh Date: Fri, 23 Oct 2020 08:09:37 +0530 Subject: [PATCH 5/7] reformat --- docs/images/http-status-code.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/images/http-status-code.md b/docs/images/http-status-code.md index 014c923..b6ab314 100644 --- a/docs/images/http-status-code.md +++ b/docs/images/http-status-code.md @@ -4,13 +4,13 @@ HTTP defines following these standard status codes that can be used to convey th The status codes are divided into the five categories. -| Status code | Description | -| :------------------- | :--------------------------------------------------------------------------------------------- | -| `1xx: Informational` | Communicates transfer protocol-level information. | -| `2xx: Success` | Indicates that the client’s request was accepted successfully. | -| `3xx: Redirection` | Indicates that the client must take some additional action in order to complete their request. | -| `4xx: Client Error` | This category of error status codes points the finger at clients. | -| `5xx: Server Error` | The server takes responsibility for these error status codes. | +| Status code | Description | +| :--------------------- | :--------------------------------------------------------------------------------------------- | +| **1xx: Informational** | Communicates transfer protocol-level information. | +| **2xx: Success** | Indicates that the client’s request was accepted successfully. | +| **3xx: Redirection** | Indicates that the client must take some additional action in order to complete their request. | +| **4xx: Client Error** | This category of error status codes points the finger at clients. | +| **5xx: Server Error** | The server takes responsibility for these error status codes. | ## Reference From 9403267f525b173375b897bfcdc40592ec7250b7 Mon Sep 17 00:00:00 2001 From: Jagadeesh Date: Fri, 23 Oct 2020 08:27:28 +0530 Subject: [PATCH 6/7] update --- docs/images/http-status-code.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/images/http-status-code.md b/docs/images/http-status-code.md index b6ab314..a5a3e71 100644 --- a/docs/images/http-status-code.md +++ b/docs/images/http-status-code.md @@ -12,6 +12,20 @@ The status codes are divided into the five categories. | **4xx: Client Error** | This category of error status codes points the finger at clients. | | **5xx: Server Error** | The server takes responsibility for these error status codes. | +## 1xx: Informational + +| Status code | Description | 🤔 | +| :---------- | :----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 100 | Continue | An interim response. Indicates 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. | +| 101 | Switching Protocol | Sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to. | + +## 2xx: Success + +| Status code | Description | 🤔 | +| :---------- | :---------- | ------------------------------------- | +| 200 | OK | Indicates that request has succeeded. | + ## Reference -[Restful API](https://restfulapi.net/http-status-codes/) +- [Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content](https://tools.ietf.org/html/rfc7231) +- [Restful API](https://restfulapi.net/http-status-codes/) From cfbb792462b7b025dd8c9e95a8c813fe6345f817 Mon Sep 17 00:00:00 2001 From: Jagadeesh Cheluvaraj Shetty Date: Sun, 22 Nov 2020 20:00:39 +0530 Subject: [PATCH 7/7] updated 2.x.x status codes. --- docs/images/http-status-code.md | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/docs/images/http-status-code.md b/docs/images/http-status-code.md index a5a3e71..7a97dec 100644 --- a/docs/images/http-status-code.md +++ b/docs/images/http-status-code.md @@ -14,16 +14,28 @@ The status codes are divided into the five categories. ## 1xx: Informational -| Status code | Description | 🤔 | -| :---------- | :----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 100 | Continue | An interim response. Indicates 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. | -| 101 | Switching Protocol | Sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to. | +| Status code | Description | 🤔 | +| :---------- | :------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 100 | Continue | An interim response. Indicates 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. | +| 101 | Switching Protocol | Sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to. | +| 102 | Processing (WebDAV) | Indicates that the server has received and is processing the request, but no response is available yet. | +| 103 | Early Hints | Primarily intended to be used with the Link header. It suggests the user agent start preloading the resources while the server prepares a final response. | ## 2xx: Success -| Status code | Description | 🤔 | -| :---------- | :---------- | ------------------------------------- | -| 200 | OK | Indicates that request has succeeded. | +| Status code | Description | 🤔 | +| :---------- | :---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 200 | OK | Indicates that request has succeeded. | +| 201 | Created | Indicates that request has succeeded and a new resource has been created as a result. | +| 202 | Accepted | Indicates that the request has been received but not completed yet. | +| | | It is typically used in log running requests and batch processing. | +| 203 | Non-Authoritative Information | Indicates that 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. | +| 204 | No Content | The server has fulfilled the request but does not need to return a response body. The server may return the updated meta information. | +| 205 | Reset Content | Indicates the client to reset the document which sent this request. | +| 206 | Partial Content | It is used when the Range header is sent from the client to request only part of a resource. | +| 207 | Multi-Status (WebDAV) | An indicator to a client that multiple operations happened, and that the status for each operation can be found in the body of the response. | +| 208 | Already Reported (WebDAV) | Allows a client to tell the server that the same resource (with the same binding) was mentioned earlier. It never appears as a true HTTP response code in the status line, and only appears in bodies. | +| 226 | IM Used | 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. | ## Reference