summary refs log tree commit diff
path: root/synapse/rest/media/v0 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove unused, undocumented "content repo" resource (#6628)Richard van der Hoff2020-01-032-103/+0
| | | | | | This looks like it got half-killed back in #888. Fixes #6567.
* Run Black. (#5482)Amber Brown2019-06-201-7/+8
|
* Port rest/ to Python 3 (#3823)Amber Brown2018-09-121-2/+2
|
* run isortAmber Brown2018-07-091-11/+8
|
* Attempt to be more performant on PyPy (#3462)Amber Brown2018-06-281-1/+2
|
* Remove the legacy v0 content upload API.Mark Haines2016-06-211-110/+2
| | | | | | The existing content can still be downloaded. The last upload to the matrix.org server was in January 2015, so it is probably safe to remove the upload API.
* Catch the exceptions thrown by twisted when you write to a closed connectionMark Haines2016-02-121-2/+2
|
* Introduce a Requester objectDaniel Wagner-Hall2016-01-111-3/+3
| | | | | | | | | 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
|
* Allow guests to register and call /events?room_id=Daniel Wagner-Hall2015-11-041-1/+1
| | | | | | | 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-1/+1
| | | | | | | | | | 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.
* Blunty replace json with simplejsonErik Johnston2015-02-111-1/+1
|
* Extract the id token of the token when authing users, include the token and ↵Mark Haines2015-01-281-1/+1
| | | | 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-1/+1
|
* Move rest APIs back under the rest directoryMark Haines2015-01-222-0/+212