So is this the normal behaviour for 5.6?
If yes, we need to document it somewhere. Other modules might be impacted.
-ovidiu
On Mon, Mar 27, 2023 at 6:57 AM Daniel-Constantin Mierla
wrote:
>
> Hello,
>
> it could be due to commit 3c1851ad546f574d1fda869348c8f7e5186079d2,
> which was done to avoid
Hello all,
How can we handle stateless replies with kemi?
tm has the following param:
modparam("tm", "on_sl_reply", "stateless_replies")
What's the proper way to map the "stateless_reply" onreply_route to a
kemi function.
I'm playing with the app_jsdt module.
Thanks,
Ovidiu
_
Hello,
On 27.03.23 14:24, Alex Balashov wrote:
> Hi,
>
> I’ve got a situation where I catch a 302 redirect in a failure_route (branch
> #1), and use the Contact to set a custom header (append_hf()).
>
> This custom header is utilised on the subsequent branch (branch #2), but if
> that branch fa
Hi,
I’ve got a situation where I catch a 302 redirect in a failure_route (branch
#1), and use the Contact to set a custom header (append_hf()).
This custom header is utilised on the subsequent branch (branch #2), but if
that branch fails (e.g. due to 4xx-5xx response), the custom header is not
Hello,
it could be due to commit 3c1851ad546f574d1fda869348c8f7e5186079d2,
which was done to avoid sharing the interpreter state before forking the
child processes.
Cheers,
Daniel
On 25.03.23 23:15, Ovidiu Sas wrote:
> Hello all,
>
> While using KEMI with app_jsdt I noticed the following possibl
