-
Notifications
You must be signed in to change notification settings - Fork 192
feat: add response header propagation #1155
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
feat: add response header propagation #1155
Conversation
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.
Quick feedback on the existing functionality: The cache header implementation needs an extensive testsuite. I suggest to split header propagation and cache header handling in two distinct core modules and different configuration. This would improve maintainability and increase awareness of the features. Caching is a complex topic and I expect more customizability in the future here (minTTL, default etc...). A dedicated config section would be great here and allow us to add more in the future.
http_cache:
enabled: true
defaultTTL: 30m
minTTL: 5m|
@jensneuse We have the requirement to propagate response header at RCCL ( Royal Caribbean ). We really appreciate the fix coming in. Please let me know timeline on this, so that we can plan accordingly. |
5a41636 to
7ad9645
Compare
… default value that will be applied
7ad9645 to
a847111
Compare
No description provided.