You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
I'm running multiple Vector instances behind AWS ALB to consume client data using an http_server listener. According to our security policy, the response must have CORS headers (Access-Control-Allow-Origin, etc.) and a few other custom ones for the client side to work. Since, as far as I know, neither ALB nor Vector have this functionality (to provide custom headers in the response), I have to use an Nginx proxy in between to provide these headers, which is an additional moving part that I wanted to get rid of.
Attempted Solutions
Nginx reverse proxy in front of Vector's http_server sink
Proposal
Logstash has 'response_headers', would be nice to have similar functionality in Vector
A note for the community
Use Cases
I'm running multiple Vector instances behind AWS ALB to consume client data using an http_server listener. According to our security policy, the response must have CORS headers (Access-Control-Allow-Origin, etc.) and a few other custom ones for the client side to work. Since, as far as I know, neither ALB nor Vector have this functionality (to provide custom headers in the response), I have to use an Nginx proxy in between to provide these headers, which is an additional moving part that I wanted to get rid of.
Attempted Solutions
Nginx reverse proxy in front of Vector's http_server sink
Proposal
Logstash has 'response_headers', would be nice to have similar functionality in Vector
References
No response
Version
No response
The text was updated successfully, but these errors were encountered: