mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-04-26 04:24:10 +02:00
Compare commits
5 commits
1d3b4dff09
...
7944d9dbe3
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
7944d9dbe3 | ||
|
|
0b5db68242 | ||
|
|
57c6273162 | ||
|
|
f49e6858f7 | ||
|
|
ba3674da8e |
|
|
@ -0,0 +1 @@
|
||||||
|
Fix various typos throughout the specification.
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Add link to JSON signing algorithm in server-server auth section for clarity. Contributed by @thetayloredman.
|
||||||
|
|
@ -84,7 +84,7 @@ For the `users` namespace, application services can only register interest in
|
||||||
homeserver). Events affecting users on other homeservers are not sent to an application
|
homeserver). Events affecting users on other homeservers are not sent to an application
|
||||||
service, even if the user happens to match the one of the `users` namespaces (unless,
|
service, even if the user happens to match the one of the `users` namespaces (unless,
|
||||||
of course, the event affects a room that the application service is interested in
|
of course, the event affects a room that the application service is interested in
|
||||||
for another room - for example, because there is another user in the room that the
|
for another reason - for example, because there is another user in the room that the
|
||||||
application service is interested in).
|
application service is interested in).
|
||||||
|
|
||||||
For the `rooms` and `aliases` namespaces, all events in a matching room will be
|
For the `rooms` and `aliases` namespaces, all events in a matching room will be
|
||||||
|
|
|
||||||
|
|
@ -277,12 +277,12 @@ queried from multiple servers to mitigate against DNS spoofing.
|
||||||
|
|
||||||
Every HTTP request made by a homeserver is authenticated using public
|
Every HTTP request made by a homeserver is authenticated using public
|
||||||
key digital signatures. The request method, target and body are signed
|
key digital signatures. The request method, target and body are signed
|
||||||
by wrapping them in a JSON object and signing it using the JSON signing
|
by wrapping them in a JSON object and signing it using the [JSON signing
|
||||||
algorithm. The resulting signatures are added as an Authorization header
|
algorithm](/appendices#signing-json). The resulting signatures are added
|
||||||
with an auth scheme of `X-Matrix`. Note that the target field should
|
as an Authorization header with an auth scheme of `X-Matrix`. Note that
|
||||||
include the full path starting with `/_matrix/...`, including the `?`
|
the target field should include the full path starting with `/_matrix/...`,
|
||||||
and any query parameters if present, but should not include the leading
|
including the `?` and any query parameters if present, but should not
|
||||||
`https:`, nor the destination server's hostname.
|
include the leading `https:`, nor the destination server's hostname.
|
||||||
|
|
||||||
Step 1 sign JSON:
|
Step 1 sign JSON:
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue