HTTP Support
Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista
Message Queuing 3.0 provides HTTP support for referencing queues, formatting messages, and HTTP message authentication.
In opening queues, direct format names can include the URL to the queue. The following two format names reference a queue that resides on a computer that is running Message Queuing. The difference between these two examples is that, unlike the first format name, the second format name invokes a secure HTTP transport through a Secure Sockets Layer (SSL) connection.
DIRECT=HTTP://MSMQComputer/msmq/MyPublicQueue
DIRECT=HTTPS://MSMQComputer/msmq/MyPublicQueue
HTTP format names can use forward slashes, "/", or backslashes, "\", to separate Message Queuing information (other format names require backslashes to separate information).
HTTP is automatically chosen as the transport for any Message Queuing message sent using an HTTP format name. In this case, the message will be formatted using the SOAP extensions for reliable messaging in the SOAP Reliable Messaging Protocol (SRMP).
A complete HTTP message, including the SOAP envelope and the SOAP attachments associated with it, can be retrieved as an array of bytes from the PROPID_M_COMPOUND_MESSAGE or MSMQMessage.CompoundMessage property. Additional application-generated header elements (PROPID_M_SOAP_HEADER or MSMQMessage.SoapHeader and application-generated SOAP body elements (PROPID_M_SOAP_BODY or MSMQMessage.SoapBody can be included in the SOAP envelope, which can be retrieved from the PROPID_M_SOAP_ENVELOPE or MSMQMessage.SoapEnvelope property.
When authentication is requested, Message Queuing automatically signs HTTP messages using an XML digital signature.
For more details, see HTTP Messages.