Bug 1042920

Summary:	Enable apps to have Node httpd redirect HTTP to HTTPS
Product:	OpenShift Container Platform	Reporter:	Keith Robertson <kroberts>
Component:	RFE	Assignee:	jofernan
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	2.0.0	CC:	ansilva, bleanhar, jkeck, jmoran, jstrong, kroberts, libra-onpremise-devel, lmeyer, lphiri
Target Milestone:	---	Flags:	lmeyer: needinfo? (kroberts)
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-11 21:00:13 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:

Description Keith Robertson 2013-12-13 16:01:23 UTC

Description of problem:
Since it is not possible to pass HTTPS connections all the way through to a JBoss gear with a HA proxy, gears of this type need the ability to manipulate their VirtualHost configuration on the OSE node such that all HTTP traffic is redirected to HTTPS.

Version-Release number of selected component (if applicable):
All

How reproducible:
Always


Expected results:
Gears have the ability to manipulate their own VirtualHost configuration in the OSE node such that the Apache server does HTTP redirection to HTTPS as described in [1].
 

Additional info:
[1] http://wiki.apache.org/httpd/RedirectSSL

Comment 2 Luke Meyer 2014-05-13 17:40:05 UTC

Under the apache-vhost frontend you could modify the HTTP template to automatically do this globally.

To do it on a per-app basis you could have the vhost HTTP template look for a marker file in the app that indicates the desire to do this, and provide the ability for the user to regenerate the frontend after changing the marker file.

Would one or the other approach fulfill the specific request adequately? Neither would address the apache-mod-rewrite frontend.