Open meshenka opened 2 months ago
just submit a first idea, not sure it should be done like that. Let me know
Hi @meshenka ,
Thanks for the associated PR #728. The truth is that Lura is not KrakenD. When KrakenD donated the framework to the Linux Foundation, a significant effort was made to "rebrand" everything in the source code and set it to Lura. KrakenD strings were removed from everywhere. This is the last thing standing, and it must go away.
While KrakenD (Enterprise) allows you to remove these headers (https://www.krakend.io/docs/enterprise/service-settings/response-headers-modifier/#example-remove-x-krakend-headers), and this is irrelevant to this conversation, Lura should not have any KrakenD string in the source code.
The future of Lura is removing all the routers and leaving the core packages only because it is not viable to maintain them all. The krakend headers will disappear from Lura when this is done.
The Krakend Gateway leaks it technology, i want to remove completely X-Krakend, X-Krakend-Completed and any X-Krakend headers from the response
Describe the solution you'd like a router configuration to be able to remove those headers
Describe alternatives you've considered I already obfuscate the gateway version, outside of this new configuration the only option i can think of is putting an nginx in front of krakend to remove those header
Additional context
< x-krakend: Version *****-v2.17.1 < x-krakend-completed: true
needs to go away
related to https://github.com/luraproject/lura/issues/445 but not quite what i need