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.
This commit is contained in:
Athanasius 2022-01-09 16:14:00 +00:00
parent 11d3501c59
commit 75c117fb12
No known key found for this signature in database
GPG Key ID: AE3E527847057C7D

View File

@ -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.