Provide option to configure "host" header in CONNECT frames to STOMP message brokers [SPR-10955]

[spring-projects-issues]

nebhale opened SPR-10955 and commented

Currently, when attempting to connect a StompRelay you can set the relay host, username, and passcode, but you cannot host that can be set in the STOMP connect frame. This means that connection strings typically returned by Cloud Foundry (http://run.pivotal.io) aren't usable. An example of this string is amqp://<username:<passcode>@turtle.rmq.cloudamqp.com/<username>.

There should be a setter for this value and it should be used by the relay when connecting.

---

Affects: 4.0 M3

Issue Links:

• No way to set virtual host in StompBrokerRelayMessageHandler [SPR-11433] #16059 No way to set virtual host in StompBrokerRelayMessageHandler

Referenced from: commits 7c37497

[spring-projects-issues]

Andy Wilkinson commented

The AMQP URI is of the form amqp://<username>:<passcode>@<host>:<port>/<vhost>. We provide setters for username, passcode, host, and port on StompBrokerRelayRegistration: setApplicationLogin, setApplicationPasscode, setRelayHost, and setRelayPort respectively. Another setter method is required so that the vhost in the URI can be provided in the Host header of the CONNECT frame.

[spring-projects-issues]

Prashant Deva commented

this is not fixed. StompBrokerRelayRegistration provides no way to set the virtual host so there is no real way to set one for StompBrokerRelayMessageHandler