Bug 1209254 - [RFE] SPDY support in OpenShift Enterprise
Summary: [RFE] SPDY support in OpenShift Enterprise
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Paul Weil
QA Contact:
URL:
Whiteboard:
Depends On: 1209253
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-06 20:27 UTC by Ricardo Martinelli de Oliveira
Modified: 2022-08-04 22:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1209253
Environment:
Last Closed: 2015-04-13 13:25:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ricardo Martinelli de Oliveira 2015-04-06 20:27:58 UTC
+++ This bug was initially created as a clone of Bug #1209253 +++

Description of problem:

Customer wants to use SPDY (http://www.chromium.org/spdy) in their OpenShift infrastructure. Also, it doesn't work because SPDY requires SSL connection. If it's possible don't terminate SSL in apache and pass it  straight to the app they can workaround that.

Comment 2 Luke Meyer 2015-04-13 13:25:02 UTC
I don't think this is relevant in v3. In v3 the frontend is not apache, and you can specify passthrough TLS (use SNI only for routing and don't terminate TLS) when you specify your external route. Feel free to reopen if the SPDY case doesn't work for some reason.


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