From 75c117fb1214bf84156b98b603bf97ce6d39e7ce Mon Sep 17 00:00:00 2001 From: Athanasius Date: Sun, 9 Jan 2022 16:14:00 +0000 Subject: [PATCH] docs/schemas: form-encoded messages are deprecated and not documented At some point I might add logging to see if any sender even *is* utilising this, and if not actually remove the possibility entirely. --- schemas/README-EDDN-schemas.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/schemas/README-EDDN-schemas.md b/schemas/README-EDDN-schemas.md index 99aaeb3..170955f 100644 --- a/schemas/README-EDDN-schemas.md +++ b/schemas/README-EDDN-schemas.md @@ -126,7 +126,8 @@ set a `Content-Type` header of `applicaton/json`, and NOT any of: * `text/plain` For historical reasons URL form-encoded data *is* supported, **but this is -deprecated and no new software should attempt this method**. +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.