diff options
| -rw-r--r-- | 98.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -46,7 +46,7 @@ Example event: | |||
| 46 | Servers MUST perform the following checks in order to validate the event: | 46 | Servers MUST perform the following checks in order to validate the event: |
| 47 | 1. The `kind` MUST be `27235`. | 47 | 1. The `kind` MUST be `27235`. |
| 48 | 2. The `created_at` MUST be within a reasonable time window (suggestion 60 seconds). | 48 | 2. The `created_at` MUST be within a reasonable time window (suggestion 60 seconds). |
| 49 | 3. The `url` tag MUST be exactly the same as the absolute request URL (including query parameters). | 49 | 3. The `u` tag MUST be exactly the same as the absolute request URL (including query parameters). |
| 50 | 4. The `method` tag MUST be the same HTTP method used for the requested resource. | 50 | 4. The `method` tag MUST be the same HTTP method used for the requested resource. |
| 51 | 51 | ||
| 52 | When the request contains a body (as in POST/PUT/PATCH methods) clients SHOULD include a SHA256 hash of the request body in a `payload` tag as hex (`["payload", "<sha256-hex>"]`), servers MAY check this to validate that the requested payload is authorized. | 52 | When the request contains a body (as in POST/PUT/PATCH methods) clients SHOULD include a SHA256 hash of the request body in a `payload` tag as hex (`["payload", "<sha256-hex>"]`), servers MAY check this to validate that the requested payload is authorized. |