summary refs log tree commit diff
path: root/synapse/rest/client/v1/pusher.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Ensure that HTML pages served from Synapse include headers to avoid embedding.Patrick Cloke2020-07-021-7/+3
|
* Clarify list/set/dict/tuple comprehensions and enforce via flake8 (#6957)Patrick Cloke2020-02-211-2/+2
| | | | Ensure good comprehension hygiene using flake8-comprehensions.
* Clean up startup for the pusher (#6558)Richard van der Hoff2019-12-181-17/+16
| | | | | | | | | | | | | | | | | | | | | | | * Remove redundant python2 support code `str.decode()` doesn't exist on python3, so presumably this code was doing nothing * Filter out pushers with corrupt data When we get a row with unparsable json, drop the row, rather than returning a row with null `data`, which will then cause an explosion later on. * Improve logging when we can't start a pusher Log the ID to help us understand the problem * Make email pusher setup more robust We know we'll have a `data` member, since that comes from the database. What we *don't* know is if that is a dict, and if that has a `brand` member, and if that member is a string.
* Port rest/v1 to async/awaitErik Johnston2019-12-051-16/+11
|
* Remove unnecessary parentheses around return statements (#5931)Andrew Morgan2019-08-301-3/+3
| | | | | Python will return a tuple whether there are parentheses around the returned values or not. I'm just sick of my editor complaining about this all over the place :)
* Replace returnValue with return (#5736)Amber Brown2019-07-231-4/+4
|
* Run Black. (#5482)Amber Brown2019-06-201-31/+39
|
* Unify v1 and v2 REST client APIs (#5226)Amber Brown2019-06-031-9/+12
|
* fix type errorAmber Brown2018-12-031-1/+1
|
* Port rest/ to Python 3 (#3823)Amber Brown2018-09-121-2/+2
|
* rename assert_params_in_request to assert_params_in_dictKrombel2018-07-131-2/+2
| | | | | | the method "assert_params_in_request" does handle dicts and not requests. A request body has to be parsed to json before this method can be used
* Use parse_{int,str} and assert from http.servletKrombel2018-07-131-10/+7
| | | | | | | parse_integer and parse_string can take a request and raise errors in case we have wrong or missing params. This PR tries to use them more to deduplicate some code and make it better readable
* run isortAmber Brown2018-07-091-7/+8
|
* Set Server header in SynapseRequestRichard van der Hoff2018-05-101-1/+0
| | | | | | | | | | | | (instead of everywhere that writes a response. Or rather, the subset of places which write responses where we haven't forgotten it). This also means that we don't have to have the mysterious version_string attribute in anything with a request handler. Unfortunately it does mean that we have to pass the version string wherever we instantiate a SynapseSite, which has been c&ped 150 times, but that is code that ought to be cleaned up anyway really.
* Burminate v1authAdrian Tschira2018-04-301-1/+1
| | | | | | | | | | | | | | | | | | This closes #2602 v1auth was created to account for the differences in status code between the v1 and v2_alpha revisions of the protocol (401 vs 403 for invalid tokens). However since those protocols were merged, this makes the r0 version/endpoint internally inconsistent, and violates the specification for the r0 endpoint. This might break clients that rely on this inconsistency with the specification. This is said to affect the legacy angular reference client. However, I feel that restoring parity with the spec is more important. Either way, it is critical to inform developers about this change, in case they rely on the illegal behaviour. Signed-off-by: Adrian Tschira <nota@notafile.com>
* Fix bug where pusherpool didn't start and broke some roomsErik Johnston2017-07-061-8/+6
| | | | | | | | Since we didn't instansiate the PusherPool at start time it could fail at run time, which it did for some users. This may or may not fix things for those users, but it should happen at start time and stop the server from starting.
* Working unsubscribe links going straight to the HSDavid Baker2016-06-021-1/+3
| | | | and authed by macaroons that let you delete pushers and nothing else
* WIP on unsubscribing email notifs without logging inDavid Baker2016-06-011-1/+54
|
* Make the /set part mandatoryDavid Baker2016-04-121-1/+1
|
* Mis-named functionDavid Baker2016-04-121-1/+1
|
* Split into separate servlet classesDavid Baker2016-04-121-11/+16
|
* Add get endpoint for pushersDavid Baker2016-04-111-1/+34
| | | | As per https://github.com/matrix-org/matrix-doc/pull/308
* Hook up adding a pusher to the notifier for replication.Mark Haines2016-03-151-0/+6
|
* Add a parse_json_object functionMark Haines2016-03-091-14/+3
| | | | | to deduplicate all the copy+pasted _parse_json functions. Also document the parse_.* functions.
* Remove dead code for setting device specific rules.Mark Haines2016-02-181-3/+3
| | | | | | It wasn't possible to hit the code from the API because of a typo in parsing the request path. Since no-one was using the feature we might as well remove the dead code.
* Fix flake8 warnings for new flake8Daniel Wagner-Hall2016-02-021-2/+2
|
* Rename 'user_name' to 'user_id' in push to make it consistent with the rest ↵Mark Haines2016-01-131-2/+2
| | | | of the code
* Introduce a Requester objectDaniel Wagner-Hall2016-01-111-2/+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
|
* also do more structured loggingDavid Baker2015-12-071-0/+1
|
* pep8David Baker2015-12-071-0/+1
|
* Add logging to pushers API to log the body of the requestDavid Baker2015-12-071-0/+4
|
* Host /unstable and /r0 versions of r0 APIsDaniel Wagner-Hall2015-12-011-2/+2
|
* 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-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.
* Allow multiple pushers for a single app ID & pushkey, honouring the 'append' ↵David Baker2015-03-251-1/+12
| | | | flag in the API.
* 1) Pushers are now associated with an access tokenDavid Baker2015-03-241-1/+2
| | | | 2) Change places where we mean unauthenticated to 401, not 403, in C/S v2: hack so it stays as 403 in v1 because web client relies on it.
* Blunty replace json with simplejsonErik Johnston2015-02-111-1/+1
|
* Code-style fixesMark Haines2015-02-101-2/+2
|
* s/instance_handle/profile_tag/David Baker2015-02-031-2/+2
|
* Allow kind to be set to null to delete a pusher.David Baker2015-01-291-1/+10
|
* Change uses of get_user_by_req because it returns a tuple now.David Baker2015-01-281-1/+1
|
* Oops, bad merge: needed to change the base class of the rest servlets too.David Baker2015-01-281-2/+2
|
* Merge branch 'develop' into pushersDavid Baker2015-01-221-0/+80
Conflicts: synapse/rest/__init__.py