-
Notifications
You must be signed in to change notification settings - Fork 336
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
reverse-proxy: T6370: Set custom HTTP headers in reverse-proxy responses #3487
Conversation
I remember that I once had an LVS load balancing solution that had not yet been merged. What’s going on now?
|
IIRC PR stalled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t see another best solution to integrate them as headers could be completely different
I wonder if we can not have a precompiled list of allowed response headers. I guess they are more common and less exotic? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Custom headers are acceptable in responses (say, X-Clacks-Overhead
) and do no harm even if clients don't use them in any way, so I see no reason to limit it to a pre-determined list.
@Mergifyio backport sagitta |
✅ Backports have been created
|
Change Summary
Add the option to set custom HTTP headers in reverse-proxy responses.
Types of changes
Related Task(s)
https://vyos.dev/T6370
Related PR(s)
Component(s) name
load-balancing -> reverse-proxy
Proposed changes
How to test
Smoketest result
Checklist: