... | ... |
@@ -1547,6 +1547,35 @@ modparam("tm", "rich_redirect", 3) |
1547 | 1547 |
... |
1548 | 1548 |
modparam("tm", "exec_time_check", 0) |
1549 | 1549 |
... |
1550 |
+</programlisting> |
|
1551 |
+ </example> |
|
1552 |
+ </section> |
|
1553 |
+ |
|
1554 |
+ <section id="tm.p.reply_relay_mode"> |
|
1555 |
+ <title><varname>reply_relay_mode</varname> (int)</title> |
|
1556 |
+ <para> |
|
1557 |
+ If set to 1, a received 200ok response that was suspeneded is no |
|
1558 |
+ longer forwarded in the transactional context if another final |
|
1559 |
+ response was forward while 200ok was suspended. Forwarding the 200ok, |
|
1560 |
+ even it was received first, results in overwritting the transaction |
|
1561 |
+ response buffer that can impact matching of incoming ACKs. |
|
1562 |
+ </para> |
|
1563 |
+ <para> |
|
1564 |
+ Set it to 0 in order to disable this behaviour and attempt to forward |
|
1565 |
+ suspended 200ok in the transaction context. This was the behaviour |
|
1566 |
+ before the commit 18410da0. |
|
1567 |
+ </para> |
|
1568 |
+ <para> |
|
1569 |
+ <emphasis> |
|
1570 |
+ Default value is 1. |
|
1571 |
+ </emphasis> |
|
1572 |
+ </para> |
|
1573 |
+ <example> |
|
1574 |
+ <title>Set <varname>reply_relay_mode</varname> parameter</title> |
|
1575 |
+ <programlisting format="linespecific"> |
|
1576 |
+... |
|
1577 |
+modparam("tm", "reply_relay_mode", 0) |
|
1578 |
+... |
|
1550 | 1579 |
</programlisting> |
1551 | 1580 |
</example> |
1552 | 1581 |
</section> |