Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1209254

Summary:	[RFE] SPDY support in OpenShift Enterprise
Product:	OpenShift Container Platform	Reporter:	Ricardo Martinelli de Oliveira <rmartine>
Component:	Networking	Assignee:	Paul Weil <pweil>
Networking sub component:	router	QA Contact:
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	dmcphers, jokerman, libra-onpremise-devel, lmeyer, mbarrett, mmccomas
Version:	3.0.0
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1209253	Environment:
Last Closed:	2015-04-13 13:25:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1209253
Bug Blocks:

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.