Feature request: allow for more flexible middlewares #1774

New Issue

MrUnknownDE · 2026-04-05T19:41:27+02:00

MrUnknownDE commented

2026-04-05 19:41:27 +02:00

Originally created by @renzos42 on 2/16/2025

Hi, I'd like the ability to not apply all optional middleware to all sites. There are cases like ForwardAuth which will be very site specific. There is no good way to achieve this at the moment. I think this feature would add a great deal of flexibility.

Atm I can think of two ways to solve this:

Define middlewares in the UI (name and textfield config), store them in the database, write them out to the dynamic dir, and provide a list in the resource settings (and hide the badgerMiddlewareName name).

Pro: Very user friendly
Con: More involved to implement
Con: Error prone due to user errors

Scan the dynamic dir for extra files (maybe with a naming convention), and provide these in a list in the resource settings (and hide the badgerMiddlewareName name).

Pro: Pretty easy to implement
Neutral: It would be a somewhat more 'advanced' hidden feature (if there are no extra middlewares, there would be nothing to select).
Con: File detection based on naming conventions or on expected values, is a bit jank.

The new access control rules cover some of the use-cases (which look super nice btw), but can never really cover the full flexibility of traefik itself (nor should it). For our case, having this missing means I cannot migrate due to some sites special config rules.

Would be great to hear any opinions on this.

*Originally created by @renzos42 on 2/16/2025* Hi, I'd like the ability to not apply all optional middleware to all sites. There are cases like `ForwardAuth` which will be very site specific. There is no good way to achieve this at the moment. I think this feature would add a great deal of flexibility. Atm I can think of two ways to solve this: 1. Define middlewares in the UI (name and textfield config), store them in the database, write them out to the dynamic dir, and provide a list in the resource settings (and hide the `badgerMiddlewareName` name). - Pro: Very user friendly - Con: More involved to implement - Con: Error prone due to user errors 2. Scan the dynamic dir for extra files (maybe with a naming convention), and provide these in a list in the resource settings (and hide the `badgerMiddlewareName` name). - Pro: Pretty easy to implement - Neutral: It would be a somewhat more 'advanced' hidden feature (if there are no extra middlewares, there would be nothing to select). - Con: File detection based on naming conventions or on expected values, is a bit jank. The new access control rules cover some of the use-cases (which look super nice btw), but can never really cover the full flexibility of traefik itself (nor should it). For our case, having this missing means I cannot migrate due to some sites special config rules. Would be great to hear any opinions on this.

MrUnknownDE closed this issue

2026-04-05 19:41:27 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1774