HTTP headers that can be used with the MQ Service Provider

The only time the MQ Service Provider expects specific HTTP headers, is when an HTTP POST is issued.

In that case the Content-Type header must be set to "application/json". If you specify a character set as part of this header, its value must be utf-8.

For example Content-Type=application/json;charset=utf-8.

Other HTTP headers can be specified on the HTTP request to change the behavior of the MQ Service Provider; these are detailed in the following sections. Any other HTTP headers are ignored.

`ibm-mq-md-msgID`

This header can be specified when issuing HTTP GET or HTTP DELETE requests to one-way services.

The value of this header is used to generate a message selector to select a message with the specified message ID. If an ibm-mq-md-correlID header is also specified, a message selector that matches both IDs will be generated.

See msgId: HTTP x-msg-msgId entity-header for details of the value of the format of this header.

`ibm-mq-md-correlID`

This header can be specified when issuing an HTTP POST, in which case it is used to set the MQMD CorrelID field of the message that gets sent.

This header can also be specified when issuing HTTP GET or DELETE requests to one-way services. The value of this header is used to generate a message selector to select a message with the specified correlation ID. If an ibm-mq-md-msgID header is also specified, a message selector that matches both will be generated.

See correlId: HTTP x-msg-correlId entity-header for details of the value of the format of this header.

`ibm-mq-pmo-retain`

You can specify this header with a value of TRUE when issuing an HTTP POST request to a one-way service backed by a topic. This results in a retained publication being generated. For more information, see Retained publications.

`ibm-mq-usr`

You can use this header to provide message properties on the IBM® MQ messages sent as a result of HTTP POST requests to both one-way and two-way services.

For details of the value of the format of this header, see usr: HTTP x-msg-usr entity-header.

Although the name used by the MQ Service Provider is different, see require-headers: HTTP x-msg-require-headers request-header for details of the value of the format of this header.