readTimeout and connectTimeout have no affect if server does return HTTP headers

When server establishes a socket connection, but never sends anything back HttpCleint gets stuck

	at java.base@11.0.14/jdk.internal.misc.Unsafe.park(Native Method)
	at java.base@11.0.14/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
	at java.base@11.0.14/java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1796)
	at java.base@11.0.14/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3128)
	at java.base@11.0.14/java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1823)
	at java.base@11.0.14/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1998)
	at platform/java.net.http@11.0.14/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:541)
	at platform/java.net.http@11.0.14/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:119)
	at app//com.github.mizosoft.methanol.Methanol$InterceptorChain.forward(Methanol.java:775)
	at app//com.github.mizosoft.methanol.Methanol$ReadTimeoutInterceptor.intercept(Methanol.java:944)
	at app//com.github.mizosoft.methanol.Methanol$InterceptorChain.forward(Methanol.java:780)
	at app//com.github.mizosoft.methanol.Methanol$AutoDecompressingInterceptor.intercept(Methanol.java:884)
	at app//com.github.mizosoft.methanol.Methanol$InterceptorChain.forward(Methanol.java:780)
	at app//com.github.mizosoft.methanol.Methanol$RequestRewritingInterceptor.intercept(Methanol.java:828)
	at app//com.github.mizosoft.methanol.Methanol$InterceptorChain.forward(Methanol.java:780)
	at app//com.github.mizosoft.methanol.Methanol.send(Methanol.java:300)

I don’t think it is a Methanol issue itself, but maybe at can be fixed with a little help from Methanol ?

[mizosoft]

Should be able to finally cut the 1.7.0 release in about a week.

[rymsha]

Great that you found time to make this! Would it be released any time soon?