[sr-dev] git:master:2fd5d881: modules: readme files regenerated - rabbitmq ... [skip ci]

Module: kamailio Branch: master Commit: 2fd5d881563126f7425730f798afcbfc2feeac65 URL: https://github.com/kamailio/kamailio/commit/2fd5d881563126f7425730f798afcbf… Author: Kamailio Dev &lt;kamailio.dev(a)kamailio.org&gt; Committer: Kamailio Dev &lt;kamailio.dev(a)kamailio.org&gt; Date: 2023-08-12T13:46:24+02:00 modules: readme files regenerated - rabbitmq ... [skip ci] --- Modified: src/modules/rabbitmq/README Modified: src/modules/xhttp/README --- Diff: https://github.com/kamailio/kamailio/commit/2fd5d881563126f7425730f798afcbf… Patch: https://github.com/kamailio/kamailio/commit/2fd5d881563126f7425730f798afcbf… --- diff --git a/src/modules/rabbitmq/README b/src/modules/rabbitmq/README index 942afffa83f..889512b6a48 100644 --- a/src/modules/rabbitmq/README +++ b/src/modules/rabbitmq/README @@ -176,7 +176,7 @@ modparam("rabbitmq", "direct_reply_to", 1) * content_type - the content_type of the messagebody. * messagebody - the messagebody to be published. - This function can be used from REQUEST_ROUTE. + This function can be used from any route. Example 1.5. rabbitmq_publish usage rabbitmq_publish("exchange", "routing_key", "application/json", "$avp(json_reque diff --git a/src/modules/xhttp/README b/src/modules/xhttp/README index 9a59c839aa1..ec009bacafb 100644 --- a/src/modules/xhttp/README +++ b/src/modules/xhttp/README @@ -83,8 +83,8 @@ Chapter 1. Admin Guide SIP parser can easily handle HTTP requests just by adding a fake Via header. - The <module>xmlrpc</module> module uses the same concept. The xHTTP - module offers a generic way of handling the HTTP protocol, by calling + The xmlrpc module uses the same concept. The xHTTP module offers a + generic way of handling the HTTP protocol, by calling event_route[xhttp:request] in your config. You can check the HTTP URL via the config variable $hu. Note that use of $ru will raise errors since the structure of an HTTP URL is not compatible with that of a SIP @@ -222,7 +222,10 @@ event_route[xhttp:request] { 6.1. xhttp:request - The event route is executed when a new HTTP request is received. + The event route is executed when a new HTTP request is received. Most + of the variables related to a SIP request can be used inside this event + route to get HTTP request attributes (e.g., $si - source IP, $hdr(X) - + body of header X, $rm - request method, $rb - request body, ...). ... tcp_accept_no_cl=yes ...