summary refs log tree commit diff
path: root/synapse/rest/client/v1/events.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Run Black. (#5482)Amber Brown2019-06-201-5/+2
|
* Unify v1 and v2 REST client APIs (#5226)Amber Brown2019-06-031-8/+9
|
* Allow client event serialization to be asyncErik Johnston2019-05-141-2/+3
|
* Port rest/ to Python 3 (#3823)Amber Brown2018-09-121-6/+6
|
* Check room visibility for /event/ requestsRichard van der Hoff2018-08-021-1/+1
| | | | | | | | Make sure that the user has permission to view the requeseted event for /event/{eventId} and /room/{roomId}/event/{eventId} requests. Also check that the event is in the given room for /room/{roomId}/event/{eventId}, for sanity.
* run isortAmber Brown2018-07-091-4/+4
|
* Make synchrotron accept /eventsErik Johnston2016-08-121-5/+4
|
* Dont invoke get_handlers fromClientV1RestServletErik Johnston2016-08-121-0/+4
| | | | | | hs.get_handlers() can not be invoked from split out processes. Moving the invocations down a level means that we can slowly split out individual servlets.
* Remove redundant exception log in /eventsErik Johnston2016-06-091-24/+21
|
* Allow non-guests to peek on rooms using /eventsDaniel Wagner-Hall2016-01-201-0/+1
|
* Introduce a Requester objectDaniel Wagner-Hall2016-01-111-7/+12
| | | | | | | | | This tracks data about the entity which made the request. This is instead of passing around a tuple, which requires call-site modifications every time a new piece of optional context is passed around. I tried to introduce a User object. I gave up.
* copyrightsMatthew Hodgson2016-01-071-1/+1
|
* Host /unstable and /r0 versions of r0 APIsDaniel Wagner-Hall2015-12-011-3/+3
|
* Open up /events to anonymous users for room events onlyDaniel Wagner-Hall2015-11-051-2/+11
| | | | Squash-merge of PR #345 from daniel/anonymousevents
* Allow guests to register and call /events?room_id=Daniel Wagner-Hall2015-11-041-2/+2
| | | | | | | This follows the same flows-based flow as regular registration, but as the only implemented flow has no requirements, it auto-succeeds. In the future, other flows (e.g. captcha) may be required, so clients should treat this like the regular registration flow choices.
* Remove completely unused concepts from codebaseDaniel Wagner-Hall2015-08-251-2/+2
| | | | | | | | | | Removes device_id and ClientInfo device_id is never actually written, and the matrix.org DB has no non-null entries for it. Right now, it's just cluttering up code. This doesn't remove the columns from the database, because that's fiddly.
* Extract the id token of the token when authing users, include the token and ↵Mark Haines2015-01-281-2/+2
| | | | device_id in the internal meta data for the event along with the transaction id when sending events
* Return the device_id from get_auth_by_reqMark Haines2015-01-281-2/+2
|
* Pass the current time to serialize event, rather than passing anMark Haines2015-01-261-1/+7
| | | | | | HS and getting a clock from it and calling time_msec on the clock. Remove the serialize_event method from the HS since it is no longer needed.
* Extract the client v1 base RestServlet to a separate classMark Haines2015-01-231-3/+3
|
* Move rest APIs back under the rest directoryMark Haines2015-01-221-0/+81