Title: Configure the Web Subsystem Describe the issue: In EAP 6.3 is added new functionality allowing to set socket binding instead of port number for port redirection. This was done as part of BZ#900786 and needs to be documented.
Added new connector option for redirect-binding to topic #4759. Changes will be visible in the next build.
Fix is available here: http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#Overview_of_HTTP_Connectors
The description of redirect-binding feature (table 16.2) explains the redirection of the http soctet connector to the https. But the example shows how to redirect ajp connector to itself - this is inconsistent and also doesn't make much sense. Please replace the command with something like: /profile=full-ha/subsystem=web/connector=http:write-attribute(name=redirect-binding,value=https) Also the link above points to the incorrect chapter 18 but the description of the redirect-binding feature is contained in the chapter 16.1.
Updated the redirect-binding example command. Changes can be verified here after the next build: http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#Configure_the_Web_Subsystem1
documentation for redirect-port is still missing. redirect-port and redirect-binding are two different connector configuration options the behavior is almost the same, just redirect-port requires number to specify port, redirect-binding requires socket-binding. Both options needs to be documented.
The CLI command is incorrect for redirect-port the value needs to be a valid port number (e.g. 8443 which is default https port number) => /profile=full-ha/subsystem=web/connector=http:write-attribute(name=redirect-port,value=8443) Next description of redirect-port is not fully correct - yes the most common case is redirection to secure connector - but note that it can be also used by redirection to ajp, see https://issues.jboss.org/browse/WFLY-1070 (mainly first three comments) Additional note: Small other suggestion for improvement. - what about having description of redirect-binding to just point that the behavior is the same as for redirect-port just the value is name of socket-binding (plus you can leave there the benefits of using socket-binding)
Formuation that the redirect-binding "acts as a connector on the http socket" is quite confusing and possibly incorrect depending on implementation details. - redirect-binding is not limited on http -> https redirection - the point of whole redirect-binding is the fact that you can use already defined socket-binding (of https, ajp, ...) to the specific port for redirection. This enables higher flexibility of configuration. Besides this the result is the same as for the redirect-port option.
Verified in Revision 6.3.0-32 - PASSED