Read and Write timeouts behavior

Question

What is the behavior of read and write timeouts in OkHttp?

Is the timeout exception triggered when the whole request exceeds the timeout duration or is when the socket doesn't receive (read) or send (write) any packet for this duration.

I think is the second behavior but could someone clarify this?

Thanks in advance.

score 24 · Accepted Answer · answered Aug 28 '15 at 11:42

24

The timeouts are triggered when you block for too long. On read that occurs if the server doesn't send you response data. On write it occurs if the server doesn't read the request you sent. Or if the network makes it seem like that's what's happening!

Timeouts are continuous: if the timeout is 3 seconds and the response is 5 bytes, an extreme case might succeed in 15 seconds just as long as the server sends something every 3 seconds. In other words, the timeout is reset after ever successful I/O.

Okio’s Timeout class also offers a deadline abstraction that is concerned with the total time spent.

answered Aug 28 '15 at 11:42

Jesse Wilson

39,078
8
121
128

Do both read and write time out happen at the client side ? or read at client side and write at server side ? thank you – Diego Ramos Oct 12 '20 at 15:22
1

Client writes time out if the the server doesn't read. Client reads timeout if the server doesn't write. – Jesse Wilson Oct 21 '20 at 00:41

Read and Write timeouts behavior

1 Answers1