Bug 900786 (JBPAPP6-1449)

Summary:	Add a redirect-port from socket-binding to the web connector config
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Coty Sutherland <csutherl>
Component:	Web	Assignee:	Emmanuel Hugonnet (ehsavoie) <ehugonne>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Radim Hatlapatka <rhatlapa>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	brian.stansberry, cdewolf, csutherl, kkhan, onagano, rhatlapa, smumford
Target Milestone:	ER1
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-1449
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	In releases of JBoss EAP prior to 6.3 socket-binding could not be used to define the redirect-port. That ability has been added in this release of the product and users can now use the new attribute redirect-binding of the connector element to define the redirect port instead of using the redirect-port attribute. This new attribute takes a socket binding name as value.	Story Points:	---
Clone Of:		Environment:	EAP 6
Last Closed:	2014-06-28 15:39:37 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Coty Sutherland 2012-08-09 15:18:36 UTC

Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000Asegn
project_key: JBPAPP6

Support configuring a connector on the http socket and then redirect to the https socket without having to specify the actual port number outside of the socket-binding-group.

The referenced forum thread has an example that uses "redirect-port" for this, but a new attribute would be needed, since changing the meaning of "redirect-port" would be incompatible.

Comment 1 Coty Sutherland 2012-08-09 15:19:23 UTC

Link: Added: This issue relates to AS7-4295

Comment 2 Coty Sutherland 2012-08-09 15:19:24 UTC

Linked is the bug logged for AS7, this one is to track this issue being reported by a customer in EAP 6.

Comment 3 Anne-Louise Tangring 2012-11-13 20:58:01 UTC

Docs QE Status: Removed: NEW

Comment 5 Osamu Nagano 2013-11-08 06:02:07 UTC

Property substitution like 'redirect-port="${jb.redirect.port:8180}"' can be a workaround but of course unifying in socket-binding is smarter.

Comment 6 Emmanuel Hugonnet (ehsavoie) 2014-03-07 11:50:55 UTC

PR: https://github.com/jbossas/jboss-eap/pull/1028
Upstream : https://github.com/wildfly/wildfly/pull/6011

Comment 9 Radim Hatlapatka 2014-04-18 13:56:22 UTC

Verified with EAP 6.3.0.ER1.

I have verified that using redirect-binding attribute of the connector, I am able to define the redirection using socket binding and that redirect-port can still be used for directly defining redirect port using a port number.

This functionality needs to be documented, I have created BZ#1089361 for it.