This commit is contained in:
Helix K 2026-04-28 17:47:01 +03:00 committed by GitHub
commit 88dcd3680c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions

View file

@ -0,0 +1 @@
Require the `destination` field in server-to-server authentication. Contributed by @velikopter.

View file

@ -375,11 +375,10 @@ The authorization parameters to include are:
`origin` field from JSON described in step 1. `origin` field from JSON described in step 1.
- `destination`: {{% added-in v="1.3" %}} the server name of the receiving - `destination`: {{% added-in v="1.3" %}} the server name of the receiving
server. This is the same as the `destination` field from the JSON described server. This is the same as the `destination` field from the JSON described
in step 1. For compatibility with older servers, recipients should accept in step 1. If the value does not match the receiving server's name, the
requests without this parameter, but MUST always send it. If this property
is included, but the value does not match the receiving server's name, the
receiving server must deny the request with an HTTP status code 401 receiving server must deny the request with an HTTP status code 401
Unauthorized. Unauthorized.
{{% changed-in v="1.19" %}} This field is now required.
- `key`: the ID, including the algorithm name, of the sending server's key used - `key`: the ID, including the algorithm name, of the sending server's key used
to sign the request. to sign the request.
- `signature`: the signature of the JSON as calculated in step 1. - `signature`: the signature of the JSON as calculated in step 1.