summary refs log tree commit diff
path: root/synapse/http/federation/well_known_resolver.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove unnecessary parentheses around return statements (#5931)Andrew Morgan2019-08-301-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 valueErik Johnston2019-08-201-11/+12
|
* Fixup changelog and remove debug loggingErik Johnston2019-08-161-4/+1
|
* Retry well known on fail.Erik Johnston2019-08-151-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 Johnston2019-08-131-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 Johnston2019-08-131-1/+4
|
* Move well known lookup into a separate clasErik Johnston2019-08-071-0/+184