the timestamps should indicate when request was requested vs received.
on the data side of thing its not logged the last time a data packet was received, and how long the transmission between packetless causing the timeout. I guess you can assume via the http request preheader (its present) there, and work backwards from the timeout error exception.
from one of my logs with default settings
Code:
----------------Request Information-------------
...
Connection-Timeout: 20000ms
Read-Timeout: 60000ms
----------------Request-------------------------
please note that I do remember some operating systems at the TCP/IP stack prevent sockets from been open without data transfer for extended periods, regardless of settings within application/client.