Bug 900786 – Add a redirect-port from socket-binding to the web connector config

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 900786 - (JBPAPP6-1449) Add a redirect-port from socket-binding to the web connector config

Summary:	Add a redirect-port from socket-binding to the web connector config

Status:	CLOSED CURRENTRELEASE

Aliases:	JBPAPP6-1449

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Web (Show other bugs)
Sub Component:
Version:	6.0.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ER1
Target Release:	EAP 6.3.0
Assigned To:	Emmanuel Hugonnet (ehsavoie)
QA Contact:	Radim Hatlapatka
Docs Contact:

URL:	http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-08-09 11:18 EDT by Coty Sutherland
Modified:	2014-06-29 18:17 EDT (History)
CC List:	7 users (show)

See Also:	1089361
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 11:39:37 EDT
Type:	Feature Request
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	AS7-4295	Major	Resolved	Add a redirect-socket configuration to the web connector config	2017-02-21 10:22 EST
JBoss Issue Tracker	JBPAPP6-1449	Major	Closed	Add a redirect-port from socket-binding to the web connector config	2017-02-21 10:22 EST
JBoss Issue Tracker	WFLY-3081	Major	Resolved	Redirect Forward port web subsystem1.6 xsd and parser from EAP 6.3	2017-02-21 10:22 EST

Groups: None (edit)

Description Coty Sutherland 2012-08-09 11:18:36 EDT

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 11:19:23 EDT

Link: Added: This issue relates to AS7-4295

Comment 2 Coty Sutherland 2012-08-09 11:19:24 EDT

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 15:58:01 EST

Docs QE Status: Removed: NEW

Comment 5 Osamu Nagano 2013-11-08 01:02:07 EST

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 06:50:55 EST

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

Comment 9 Radim Hatlapatka 2014-04-18 09:56:22 EDT

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.

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