it is in the nature of tcp (and, therefore, the underlying okhttp3 api) to retry until it gets an
acknowledgment or to hang up either after a certain time or a certain number of failures.
if your device does not receive the expected acknowledgment, it will try again (silently).
if you search online for okhttp3 (what okhttputils2 is based on), you will see the matter is
an ongoing topic of discussion. you would need to write your own okhttp3 client to modify
this (which, in any case, is discouraged). the whole intent of tcp is to do everything
possible to guarantee faithful transmission of the request. a poor network connection
would interfere with this.