-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global UpstreamHeaderTransform settings in GlobalConfiguration section #1658
Comments
Hi Mark! Thanks for paying your attention to this per Route feature. Do you have some preliminary solution? Did you fork the Ocelot repo? If you've seen someone's solution, just let me know about please! |
@abooraja @anktsrkr @binarymash @briansantura @geffzhang @jps @margaale @philproctor @TomPallister |
I do not currently have a solution for it no, but I'd say it would be pretty easy to implement. Could be a new Then, if there is a header transform set on a route which is also a default, that would "win" over the default one (so you can override specific headers on specific routes). |
Added a PR |
👌 I believe this local-to-global feature enhancement will be useful for the Ocelot community. |
Is it solved? I urgently need this feature |
Hi 老中医 ! |
Any ETA to release this feature? |
@spaduret |
New Feature
Add UpstreamHeaderTransform globally for all routes.
Motivation for New Feature
Currently we have to set the same transforms on all routes, leaving a lot of copy paste work.
A solution would be to also set global transforms in
GlobalConfiguration
Related to
Feature: Headers Transformation
The text was updated successfully, but these errors were encountered: