Repository navigation
fix(vibetype): remove the stale cors middleware reference - #323
Merged
dargmuesli merged 2 commits intoOct 27, 2026
Merged
Conversation
dargmuesli
deleted the
fix/vibetype/remove-stale-cors-middleware-reference
branch
October 27, 2026 12:31
maevsi-bot
pushed a commit
that referenced
this pull request
Oct 27, 2026
## [21.7.3](21.7.2...21.7.3) (2026-10-27) ### Bug Fixes * **vibetype:** remove the stale cors middleware reference ([#323](#323)) ([e73a850](e73a850))
|
🎉 This PR is included in version 21.7.3 🎉 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.
The port-80 router's production middleware list referenced the CORS middleware under a name that does not exist, so the reverse proxy keeps logging an error for the missing middleware.
The stale reference is a leftover from a rename that updated the middleware definition but not this label.
The reference is removed rather than corrected: the middleware never took effect, the application emits its own CORS headers, and the scheme redirect at the start of the list already ends every port-80 request before anything else in the chain runs.
The commented-out beta routers are aligned with their live counterparts: the port-80 list mirrors the live router, and the secure list gets the corrected middleware name.
Re-enabling them therefore does not reintroduce the broken reference or the plain-HTTP behavior.