diff options
author | sigiesec <simon.giesecke@btc-ag.com> | 2016-02-02 11:59:30 +0100 |
---|---|---|
committer | sigiesec <simon.giesecke@btc-ag.com> | 2016-02-02 11:59:30 +0100 |
commit | 5b5d8a668cda595498125ac26654b59f7235e63b (patch) | |
tree | c93a1c684d340f827b5c496d40ba28120143a311 /librabbitmq | |
parent | 865dedbccca696b01f99fe56ad3871b1abfa8eb6 (diff) | |
download | rabbitmq-c-5b5d8a668cda595498125ac26654b59f7235e63b.tar.gz |
Documentation of amqp_basic_publish references wrong AMQP methodpr340
The documentation of amqp_basic_publish incorrectly states that the
broker will respond with a basic.reject method in case of failures when
the mandatory or immediate flags are set. Actually, this is the
basic.return method.
Diffstat (limited to 'librabbitmq')
-rw-r--r-- | librabbitmq/amqp.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/librabbitmq/amqp.h b/librabbitmq/amqp.h index c699a83..724c8f5 100644 --- a/librabbitmq/amqp.h +++ b/librabbitmq/amqp.h @@ -1875,10 +1875,10 @@ struct amqp_basic_properties_t_; * \param [in] routing_key the routing key to use when publishing the message * \param [in] mandatory indicate to the broker that the message MUST be routed * to a queue. If the broker cannot do this it should respond with - * a basic.reject method. + * a basic.return method. * \param [in] immediate indicate to the broker that the message MUST be delivered * to a consumer immediately. If the broker cannot do this it should - * response with a basic.reject method. + * response with a basic.return method. * \param [in] properties the properties associated with the message * \param [in] body the message body * \return AMQP_STATUS_OK on success, amqp_status_enum value on failure. Note |