tree 5f06d16ceb43b5e6e82085f3cb353619add14e37
parent 816fc22a4a618bde48f6dd5e32499fa1459279b5
author Willy Tarreau <w@1wt.eu> 1254646568 +0200
committer Willy Tarreau <w@1wt.eu> 1254646568 +0200
encoding latin1

[BUG] don't refresh timeouts late after detected activity

In old versions, before 1.3.16, we had to refresh the timeouts after
each call to process_session() because the stream socket handler did
not do it. Now that the sockets can exchange data for a long period
without calling process_session(), we can detect an old activity and
refresh a timeout long after the last activity, causing too late a
detection of some timeouts.

The fix simply consists in not checking for activity anymore in
stream_sock_data_finish() but only set a timeout if it was not
previously set.