-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
(feature) Disable version header in relay proxy #3140
Comments
/assign-me |
👋 Hey @tomflenner, this issue is already assigned to @thomaspoignant. 🔧 A maintainer can also add you to the list of assignees or swap you with the current assignee. |
/assign-me |
👋 Hey @tomflenner, thanks for your interest in this issue! 🎉 ⚠ Note that this issue will become unassigned if it isn't closed within 20 days. 🔧 A maintainer can also add the 📌 Pinned label to prevent it from being unassigned automatically. |
add a boolean EnableVersionHeader in configuration to conditionnally register the VersionHeader custom middleware and disable the header x-gofeatureflag-version issue: thomaspoignant#3140
add a boolean EnableVersionHeader in configuration to conditionnally register the VersionHeader custom middleware and disable the header x-gofeatureflag-version issue: thomaspoignant#3140
add a boolean EnableVersionHeader in configuration to conditionnally register the VersionHeader custom middleware and disable the header x-gofeatureflag-version issue: thomaspoignant#3140
add a boolean DisableVersionHeader in configuration with Skipper on the VersionHeader middleware to issue: thomaspoignant#3140
add a boolean EnableVersionHeader in configuration to conditionnally register the VersionHeader custom middleware and disable the header x-gofeatureflag-version issue: thomaspoignant#3140
add a boolean DisableVersionHeader in configuration with Skipper on the VersionHeader middleware to issue: thomaspoignant#3140
* feat(relayproxy): allow disable VersionHeader middleware add a boolean EnableVersionHeader in configuration to conditionnally register the VersionHeader custom middleware and disable the header x-gofeatureflag-version issue: #3140 * feat(relayproxy): allow disable VersionHeader middleware add a boolean DisableVersionHeader in configuration with Skipper on the VersionHeader middleware to issue: #3140 * docs(relayproxy): add disableVersionHeader to documentation * feat(relayproxy): fix linter with non used parameter in Skipper * nit pick to be more idiomatic Signed-off-by: Thomas Poignant <[email protected]> --------- Signed-off-by: Thomas Poignant <[email protected]> Co-authored-by: Tom Flenner <[email protected]> Co-authored-by: Thomas Poignant <[email protected]>
Requirements
Hello !
We're using RelayProxy in production since several month now and our OPS teams reported that the
x-gofeatureflag-version
header was forward in HTTP requests. It would be nice to not have to tweak our Kong gateway to remove this header and let the component himself do it. Our team don't want to expose infrastructure concern inside the HTTP request for some reason.After discussing with @thomaspoignant, this header is used to detect GOFF version and disable some feature in the provider for compatibility reason. At the moment he never needed to use this feature.
I suggest to allow users to deactivate this header from configuration to be more flexible on relay proxy usage.
The text was updated successfully, but these errors were encountered: