[MXS-3003] Support inbound proxy protocol Created: 2020-05-22 Updated: 2023-03-08 Resolved: 2023-02-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | 23.02.0 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Laurent Indermühle | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-171, MXS-SPRINT-174, MXS-SPRINT-175, MXS-SPRINT-176 |
| Description |
|
It would be nice if MaxScale could support inbound proxy_protocol connections. Even nicer if it can forward the received headers to the backend also using proxy_protocol. This will enable the usage of a load-balancer in front of MaxScale and still gain the simplification of MariaDB account management. The end goal is to have a high availability setup of MaxScale without using any virtual IP address or KeepAlived services. |
| Comments |
| Comment by markus makela [ 2020-05-22 ] |
|
This would also fix the case where one MaxScale points to another MaxScale and both use proxy_protocol. |