Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Be stricter about JSON that is accepted by Synapse (#8106) | Patrick Cloke | 2020-08-19 | 1 | -3/+2 |
| | |||||
* | Include a user agent in federation requests. (#7677) | Patrick Cloke | 2020-06-16 | 1 | -2/+15 |
| | |||||
* | Remove unnecessary parentheses around return statements (#5931) | Andrew Morgan | 2019-08-30 | 1 | -1/+1 |
| | | | | | 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 :) | ||||
* | Change jitter to be a factor rather than absolute value | Erik Johnston | 2019-08-20 | 1 | -11/+12 |
| | |||||
* | Fixup changelog and remove debug logging | Erik Johnston | 2019-08-16 | 1 | -4/+1 |
| | |||||
* | Retry well known on fail. | Erik Johnston | 2019-08-15 | 1 | -22/+100 |
| | | | | | | If we have recently seen a valid well-known for a domain we want to retry on (non-final) errors a few times, to handle temporary blips in networking/etc. | ||||
* | Retry well-known lookup before expiry. | Erik Johnston | 2019-08-13 | 1 | -22/+60 |
| | | | | | | | | | This gives a bit of a grace period where we can attempt to refetch a remote `well-known`, while still using the cached result if that fails. Hopefully this will make the well-known resolution a bit more torelant of failures, rather than it immediately treating failures as "no result" and caching that for an hour. | ||||
* | Make default well known cache global again. | Erik Johnston | 2019-08-13 | 1 | -1/+4 |
| | |||||
* | Move well known lookup into a separate clas | Erik Johnston | 2019-08-07 | 1 | -0/+184 |