fix(pusher): Unify retry backoff and fix proxied or LAN push gateways #2261

Merged

Jade merged 3 commits from eleboucher/continuwuity:refactor/unify-federation-backoff into main 2026-10-12 10:29:21 +00:00

Conversation 1 Commits 3 Files changed 11 +156 -71

eleboucher commented 2026-09-17 08:07:51 +00:00

Contributor

Copy link

• Unify retry backoff helpers across federation, sending, event handling and web push
• Resolve pusher hostnames and check them against ip_range_denylist at registration and before every send (previously only literal IPs were checked, and the post-connect check fired after the push was already delivered)
• A forbidden web push endpoint no longer triggers retries and backoff
• Log forbidden-address rejections at warn
• Don't reject pushes through a forward proxy on a private address; HTTP(S)/socks4a/socks5h proxies resolve names remotely and must enforce the denylist themselves
• Only strip notification_push_path when it is a suffix of the pusher URL, and clarify its docs

Pull request checklist:

• This pull request targets the main branch, and the branch is named something other than
  main.
• I have written an appropriate pull request title and my description is clear.
• I understand I am responsible for the contents of this pull request.
• I have followed the contributing guidelines:
  • My contribution follows the code style, if applicable.
  • I ran pre-commit checks before opening/drafting this pull request.
  • I have tested my contribution (or proof-read it for documentation-only changes)
    myself, if applicable. This includes ensuring code compiles.
  • My commit messages follow the commit message format and are descriptive.

<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> - Unify retry backoff helpers across federation, sending, event handling and web push - Resolve pusher hostnames and check them against ip_range_denylist at registration and before every send (previously only literal IPs were checked, and the post-connect check fired after the push was already delivered) - A forbidden web push endpoint no longer triggers retries and backoff - Log forbidden-address rejections at warn - Don't reject pushes through a forward proxy on a private address; HTTP(S)/socks4a/socks5h proxies resolve names remotely and must enforce the denylist themselves - Only strip notification_push_path when it is a suffix of the pusher URL, and clarify its docs <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [ ] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages

forgejo-actions added the

Dependencies

Changelog

Added

labels 2026-09-17 08:07:55 +00:00

eleboucher changed title from WIP: refactor: Unify retry backoff helpers to refactor: Unify retry backoff helpers 2026-09-23 18:52:07 +00:00

eleboucher force-pushed refactor/unify-federation-backoff from cae15590b0 to ca33d48155 2026-09-23 19:02:14 +00:00 Compare

forgejo-actions added

Changelog

Missing

and removed

Changelog

Added

labels 2026-09-23 19:02:21 +00:00

eleboucher changed title from refactor: Unify retry backoff helpers to fix(pusher): Unify retry backoff and fix proxied or LAN push gateways 2026-09-23 19:26:12 +00:00

eleboucher force-pushed refactor/unify-federation-backoff from ca33d48155 to 2a16561ff0 2026-09-26 09:54:07 +00:00 Compare

eleboucher force-pushed refactor/unify-federation-backoff from 2a16561ff0 to d8103910ea 2026-09-28 06:54:30 +00:00 Compare

eleboucher force-pushed refactor/unify-federation-backoff from d8103910ea to 33ddd87283 2026-09-28 06:58:25 +00:00 Compare

forgejo-actions added

Changelog

Added

and removed

Changelog

Missing

labels 2026-09-28 06:58:32 +00:00

Jade force-pushed refactor/unify-federation-backoff from 33ddd87283 to 757cf9f7e8 2026-10-04 22:31:39 +00:00 Compare

Jade force-pushed refactor/unify-federation-backoff from 757cf9f7e8 to 9d6c3d4200 2026-10-04 23:28:50 +00:00 Compare

stratself approved these changes 2026-10-10 04:29:46 +00:00

stratself left a comment

Copy link

Works as intended

Works as intended

Jade force-pushed refactor/unify-federation-backoff from 9d6c3d4200 to 24e289113b 2026-10-12 10:15:20 +00:00 Compare

Jade merged commit 24e289113b into main 2026-10-12 10:29:21 +00:00

Jade deleted branch refactor/unify-federation-backoff 2026-10-12 10:29:21 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

stratself

Labels

Clear labels   

Abandoned

This pull request appears to be abandoned by its author.

  

Blocked

This pull request or issue is currently blocked from being merged/closed

  

Bug

Something isn't working as intended

  

Changelog

Added

Changelog entry added

  

Changelog

Missing

No changelog when one is needed

  

Changelog

None

Changelog is unnecesary for this change

  

Cherry-picking

Commits picked from other conduit projects

  

Database

This requires or includes changes to the database

  

Dependencies

Something dependency related

  

Dependencies/Renovate

Automatic dependency upgrades by Renovate

  

Difficulty

Easy

Low difficulty to implement - touches few parts of the codebase, low complexity

  

Difficulty

Hard

High difficulty to implement - touches many parts of the codebase, high complexity

  

Difficulty

Medium

Medium difficulty to implement - touches more parts of the codebase, higher complexity

  

Documentation

Improvements or additions to documentation

  

Enhancement

New feature or request

  

Good first issue

Good for newcomers

  

Help wanted

Additional eyes and keyboards are required for this one

  

Inherited

Issues that have been inhereted from the project pre-fork

  

Matrix/Administration

Features pertaining to homeserver administration

  

Matrix/Appservices

Features pertaining to the appservice API

  

Matrix/Auth

Features pertaining to authentication

  

Matrix/Client

Features pertaining to client-to-server interactions

  

Matrix/Core

Issues relating to core matrix functionality, such as state resolution and PDU formats

  

Matrix/E2EE

Issues related to end to end encryption

  

Matrix/Federation

Features pertaining to server-to-server interactions

  

Matrix/Hydra

Issues related to room version 12 and related changes (temporary label)

  

Matrix/MSC

Features pertaining to unstable matrix features

  

Matrix/Media

Features pertaining to media interactions

  

Matrix/T&S

Changes or issues related to trust & safety tooling

  

Merge

This PR is ready to be merged

  

Merge/Manual

This PR should be manually merged

  

Merge/Squash

This PR should be squashed when it is merged

  

Meta

Related to housekeeping, maintenance, or other repo-meta.

  

Meta/CI

Issues related to CI changes

  

Meta/Packaging

Packaging

  

Priority

Blocking

This issue is blocking the next release

  

Priority

High

This issue is very important

  

Priority

Low

This issue is of a rather low priority

  

Security

This item is related to general security

  

Status

Confirmed

This issue has enough information and is confirmed

  

Status

Duplicate

This issue or pull request already exists

  

Status

Invalid

This issue doesn't seem right

  

Status

Needs Investigation

This issue needs further investigation

  

Support

Questions or support requests

  

bob the builder

pdu logic rewrite starring nexus nicholson

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

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

continuwuation/continuwuity!2261

No description provided.