You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Eykhler Vladimir (JIRA)" <ji...@apache.org> on 2016/07/04 09:40:10 UTC
[jira] [Created] (APLO-393) List of the allowed host names of the
virtual host is case-sensitive
Eykhler Vladimir created APLO-393:
-------------------------------------
Summary: List of the allowed host names of the virtual host is case-sensitive
Key: APLO-393
URL: https://issues.apache.org/jira/browse/APLO-393
Project: ActiveMQ Apollo
Issue Type: Bug
Components: apollo-broker
Affects Versions: 1.7.1
Environment: Windows 7 x64, jdk 1.7.0.60, STOMP
Reporter: Eykhler Vladimir
Priority: Minor
Apollo.xml contains one virtual host with host names list:
{code}
<broker xmlns="http://activemq.apache.org/schema/activemq/apollo">
...
<virtual_host id="default">
<host_name>SERVER_NAME</host_name>
<null_store/>
</virtual_host>
<connector id="tcp" bind="tcp://SERVER_NAME:61613" connection_limit="2000"/>
</broker>
{code}
The application connect to the broker through the Apache.NMS.Stomp client library by specifying a broker address and port as URI string (tcp://SERVER_NAME:PORT), the scheme and host portion of URI is case insensitive (by [RFC 3986|http://tools.ietf.org/html/rfc3986]) and SERVER_NAME could be normalized to lower case ('server_name'). Now, if connecting to a broker with URI of *tcp://server_name:port* receiving an error
{code}
Command: ERROR
Header: message:Invalid virtual host\c server_name
{code}
After adding host_name tag with host name in lower case (server_name) to apollo.xml configuration file the error is gone.
But I don't see where case-sensitive host names can be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)