Are there any plans to add proxy protocol support for akka-http? If not, how difficult would it be to manually configure in support via a flow/stage?
The reason we needed is specific but possibly not uncommon:
- we currently use akka-http to provide a websocket api which works very well
- we deploy on AWS
- we use an AWS Elastic load balancer to distribute traffic to our websocket instances
The above all works without issue, but we now need to identify the IP addresses that the websocket connections originate from.
For HTTP(S) connections, AWS ELB adds an X-Forwarded-For header which is already supported in akka-http. However, in order to use AWS ELB for websocket connections, the ELB needs to be configured to listen using TCP rather than HTTP which means there is no X-Forwarded-For header and instead the proxy protocol is used.
We already have a stateful stage that manages the proxy protocol for our TCP connections but what I need some guidance with is how to use that when using the HTTP bindings. Any ideas?
Thanks,
Julian