Description

For our http-intensive application we wrap okhttp with a domain-specific client using logbook for logging.
To test end-to-end, we use wiremock faults to simulate IO Problems and validate the application level result is as required.

While upgrading from logbook 3.7.2 to 3.12.1, the MALFORMED_RESPONSE_CHUNK test fails and seems to crush okhttp own thread.

Expected Behavior

logbook okhttp interceptor does not affect, in no circumstances, the result of the request or response in the application.

Actual Behavior

a MALFORMED_RESPONSE_CHUNK simulation of wiremock causes an exception to be thrown in okhttp managed thread.

Possible Fix