Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1594957 - [RFE] Router pod use send-proxy-v2
Summary: [RFE] Router pod use send-proxy-v2
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-25 20:01 UTC by Eric Jones
Modified: 2019-02-11 18:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Jones 2018-06-25 20:01:56 UTC
- What is the nature and description of the request? 
As an admin I require the ability to use Applications requiring SNI Headers and Path Based Routing (sni currently works with passthrough but that doesn't allow for pathbased routing).

- Why does the customer need this? (List the business requirements here) 
To take advantage of IBM's Security Acess Manager for Mutual Authentication with specific path based applications.

- How would the customer like to achieve this? (List the functional requirements here) 
Changing the send-proxy in the router pod from v1 to v2:

OLD:
backend be_sni
  server fe_sni 127.0.0.1:{{env "ROUTER_SERVICE_SNI_PORT" "10444"}} weight 1 send-proxy


NEW:
backend be_sni
  server fe_sni 127.0.0.1:{{env "ROUTER_SERVICE_SNI_PORT" "10444"}} weight 1 send-proxy-v2

This should allow other secured routes (besides passthrough) to use SNI headers


- Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I could find


Note You need to log in before you can comment on or make changes to this bug.