-
Notifications
You must be signed in to change notification settings - Fork 428
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow JIDs from all MUC light domains in HTTP room API
- Loading branch information
Showing
3 changed files
with
31 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,7 +10,7 @@ info: | |
This is to ensure integration between the **REST API** users and regular **XMPP** users. | ||
* All requests requiring a room ID (i.e. most of the requests fired at `/room` endpoint) accept either | ||
a bare room ID (e.g. `656c6f656c6f`) or a room JID (e.g. `[email protected]`). | ||
The host part of the room JID must be the host name of a MUC light service running in user's domain. | ||
The host part of the room JID must be the host name of a registered MUC light service. | ||
* All requests require authentication. | ||
This is to make sure the server can identify who sent the request and if it comes from an authorized user. | ||
Currently the only supported method is **Basic Auth**. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters