[MDEV-15501] Dynamic config `proxy_protocol_networks` Created: 2018-03-07 Updated: 2018-03-24 Resolved: 2018-03-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Fix Version/s: | 10.3.6 |
| Type: | Task | Priority: | Major |
| Reporter: | dapeng huang | Assignee: | Vladislav Vaintroub |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 10.3.6-1 | ||||||||
| Description |
|
Current Implication of proxy protocol is not very convenient，proxy_protocol_networks is read only, so when we need deploy a proxy which not belong to proxy_protocol_networks, then we need change the server's config and restart. And for the aspect of safety, we cannot config a big subnet, maybe just add proxy's ip to proxy_protocol_networks |
| Comments |
| Comment by Vladislav Vaintroub [ 2018-03-07 ] |
|
proxy_protocol_networks are masks, not IP addresses, so you definitely can add a new IP as long as it is subnet conforming, and do so without a restart. You can always add any proxy, if the value is * (not recommended, obviously) |
| Comment by Vladislav Vaintroub [ 2018-03-07 ] |
|
You do not have to have a big subnet either. You can have a small subnet too |
| Comment by dapeng huang [ 2018-03-07 ] |
|
In some situation, we may add more node for proxy cluster, and cannot determine which subnet of new node in advance, so need dynamic config |