]
Brian Stansberry commented on AS7-5871:
---------------------------------------
Are there any reports of this issue causing any actual problem other than a strange value
in a read of the connector resource?
The way the integration of this resource is written[1] the default value isn't passed
into the JBoss Web layers at all, and the org.apache.catalina.connector.Connector
class' default value of 443 will be used. I've looked all the way back to the
beginning of the web subsystem and this has always been the case.
Given this, the proper fix here may be to remove the default value from the attribute
definition altogether. That will result in consistent behavior with between EAP 6.0 and
EAP 6.1 and with earlier AS 7.x releases.
[1]
The default redirect port for the 8080 connector is current 8433.
Should be 8443 instead.
------------------------------------------------------------------------------------------
Key: AS7-5871
URL:
https://issues.jboss.org/browse/AS7-5871
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.3.Final (EAP)
Reporter: Wolf-Dieter Fink
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
The default redirect port for the 8080 connector is 8433. Seems that this is wrong as
socket-bindings use 8443 (and former releases also)
[standalone@localhost:9999 /] /subsystem=web/connector=http:read-resource
{
"outcome" => "success",
"result" => {
...,
"name" => "http",
"protocol" => "HTTP/1.1",
"redirect-port" => 8433,
"scheme" => "http",
"secure" => false,
"socket-binding" => "http",
"ssl" => undefined,
"virtual-server" => undefined
}
}
The pre-configured "https" socket binding conversely is 8443:
[standalone@localhost:9999 socket-binding=https]
/socket-binding-group=standard-sockets/socket-binding=https:read-resource
{
"outcome" => "success",
"result" => {
"client-mappings" => undefined,
"fixed-port" => false,
"interface" => undefined,
"multicast-address" => undefined,
"multicast-port" => undefined,
"name" => "https",
"port" => 8443
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: