[RFE] Add support X-Forwarded-For header in LBaaSv2
Bug #1523219 reported by
Kobi Samoray
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
X-Forwarded-For headers are used by proxies and load balancers to pass on the original client's IP to the server, while NATing the request.
This is very handy for some applications but has some overheads and therefore has to be configurable.
LBaaSv2 API doesn't offer support for enabling XFF header.
Without having an XFF header, the members cannot conclude which IP address originated the NATed request - e.g for auditing purposes.
Changes required are addition of a boolean property to the listener - which will indicate that an XFF header should be appended to the requests.
Changed in neutron: | |
assignee: | nobody → Kobi Samoray (ksamoray) |
tags: | added: lbaas |
tags: | added: rfe |
summary: |
- No support for X-Forwarded-For header in LBaaSv2 + [RFE] Support X-Forwarded-For header in LBaaSv2 |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in neutron: | |
status: | Confirmed → Triaged |
tags: | added: rfe-approved |
tags: | removed: rfe |
tags: |
added: rfe removed: rfe-approved |
description: | updated |
summary: |
- [RFE] Support X-Forwarded-For header in LBaaSv2 + [RFE] Add support X-Forwarded-For header in LBaaSv2 |
Changed in neutron: | |
status: | Triaged → In Progress |
Changed in neutron: | |
milestone: | none → mitaka-2 |
Changed in neutron: | |
milestone: | mitaka-2 → mitaka-3 |
Changed in neutron: | |
assignee: | nobody → Kobi Samoray (ksamoray) |
status: | Incomplete → In Progress |
affects: | neutron → octavia |
To post a comment you must log in.
Should this be an RFE?