Repository navigation
fix(traefik): redirect http to https in production - #322
Merged
dargmuesli merged 2 commits intoOct 27, 2026
Merged
Conversation
dargmuesli
deleted the
fix/traefik/redirect-http-to-https-in-production
branch
October 27, 2026 11:51
maevsi-bot
pushed a commit
that referenced
this pull request
Oct 27, 2026
## [21.7.2](21.7.1...21.7.2) (2026-10-27) ### Bug Fixes * **traefik:** redirect http to https in production ([#322](#322)) ([a5418cd](a5418cd))
|
🎉 This PR is included in version 21.7.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In production the reverse proxy's port-80 entry point forwarded requests to the origin services, which answered plain-HTTP requests with a full 200 OK instead of redirecting to HTTPS.
The scheme-redirect middleware that performs the 301 was only attached to the port-80 routers in development.
The middleware definition and all port-80 routers now use the middleware in production as well, and the production overrides of
vibetypeandtusd, which define their port-80 middleware list, include it in that list too.