Christopher Faulet 2c672f282d BUG/MEDIUM: stconn: Allow expiration update when READ/WRITE event is pending ... When a READ or a WRITE activity is reported on a channel, the corresponding date is updated. the last-read-activity date (lra) is updated and the first-send-block date (fsb) is reset. The event is also reported at the channel level by setting CF_READ_EVENT or CF_WRITE_EVENT flags. When one of these flags is set, this prevent the update of the stream's task expiration date from sc_notify(). It also prevents corresponding timeout to be reported from process_stream(). But it is a problem during fast-forwarding stage if no expiration date was set by the stream. Only process_stream() resets these flags. So a first READ or WRITE event will prevent any stream's expiration date update till a new call to process_stream(). But with no expiration date, this will only happen on shutdown/abort event, blocking the stream for a while. It is for instance possible to block the stats applet or the cli applet if a client does not consume the response. The stream may be blocked, the client timeout is not respected and the stream can only be closed on a client abort. So now, we update the stream's expiration date, regardless of reported READ/WRITE events. It is not a big deal because lra and fsb date are properly updated. It also means an old READ/WRITE event will no prevent the stream to report a timeout and it is expected too. This patch must be backported as far as 2.8. On older versions, timeouts and stream's expiration date are not updated in the same way and this works as expected.		2024-02-14 14:22:36 +01:00
..
haproxy	BUG/MEDIUM: stconn: Allow expiration update when READ/WRITE event is pending	2024-02-14 14:22:36 +01:00
import	IMPORT: ebtree: make string_equal_bits() return an unsigned	2024-01-06 13:35:42 +01:00
make	BUILD: makefile: also define cmd_CXX to pretty-print C++ build commands	2024-01-26 18:54:23 +01:00