third-party-mirrors/EDDN
1
0
Fork 0
mirror of https://github.com/EDCD/EDDN.git synced 2025-04-19 18:17:37 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

schemas/README: If using compression, set Content-Type correctly

Browse Source
This commit is contained in:
Athanasius 2022-01-28 13:01:53 +00:00
parent e50b57a538
commit 4aadbeb146
No known key found for this signature in database
GPG Key ID: AE3E527847057C7D
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
schemas/README-EDDN-schemas.md
View File

@ -118,7 +118,7 @@ Messages sent to EDDN **MUST**:
- Use a **POST** request, with the body containing the EDDN message. No
query parameters in the URL are supported or necessary.
The body of an EDDN message is a JSON object in UTF-8 encoding. You SHOULD
The body of an EDDN message is a JSON object in UTF-8 encoding. You MUST
set a `Content-Type` header of `applicaton/json`, and NOT any of:
* `application/x-www-form-urlencoded`
@ -130,7 +130,8 @@ deprecated and no new software should attempt this method**. We
purposefully do not further document the exact format for this.
You *MAY* use gzip compression on the body of the message, but it is not
required.
required. If you do compress the body then you **MUST* send a `Content-Type`
header with `gzip` value instead of `application/json`.
You should be prepared to handle all scenarios where sending of a message
fails: