68
edits
Loop/Architecture/Rooms: Difference between revisions
Jump to navigation
Jump to search
→Refreshing Membership in a Room
No edit summary |
|||
| Line 353: | Line 353: | ||
==== Refreshing Membership in a Room ==== | ==== Refreshing Membership in a Room ==== | ||
* For a desktop client user, the "Authorization" header field is populated with the HAWK token (using a scheme of "Hawk"), just like it is for other requests. | |||
* For the standalone client, the "Authorization" header field is encoded using [http://tools.ietf.org/html/rfc1945#section-11.1 Basic authentication]. The user ID portion is the sessionToken provided to the user when they joined the room, and the password is blank. | |||
POST /rooms/QzBbvGmIZWU HTTP/1.1 | POST /rooms/QzBbvGmIZWU HTTP/1.1 | ||