Validate/add support for refreshing cached servers (e.g. server well-knowns) #64
Labels
No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If a user has a bad well-known (invalid Content-Type, wrong server, etc) and fixed it later, Conduit may or may not have that bad server well-known cached until Conduit is restarted which isn't ideal, especially if compaction takes a long time for some users. This may result in Conduit falsely thinking the server is down as said requests would be failing when Conduit just needs to re-get the server well-known.
Should validate that this is the case, and if it is: add support for automatically clearing cached servers when requests fail. If subsequent requests fail after clearing cache, then exponential backoff should start kicking in.
I suspect this is why I have trouble connecting to mozilla.org sometimes and falls back to sending failing requests to
mozilla.org:8448.This should be enough:
github.com/girlbossceo/conduwuit@0297cfe307I don't think a command to evict all cached destinations is a good idea since that seems to be a ton of servers cached and we should only focus on the ones that we send requests to and fail and need to attempt to retry getting well-known.