// the find
lysine-dev/okhttp
A meticulous HTTP client for the JVM, Android, and GraalVM.
OkHttp is Square's HTTP client for the JVM, Android, and GraalVM native images, handling connection pooling, HTTP/2 multiplexing, transparent GZIP, and response caching. It's aimed at anyone writing network code in Kotlin/Java who wants a client that's already solved the hard parts of HTTP correctness rather than rolling their own on top of raw sockets or java.net.HttpURLConnection.
Backed by real RFC conformance (9110-9113, websockets, SSE) rather than vague 'HTTP support' claims, and it explicitly tracks the TLS ecosystem over time instead of letting cert/cipher support rot. Ships as a proper Kotlin Multiplatform artifact with Java 9 module boundaries enforced, so you can't accidentally depend on internals that'll break on a minor bump. MockWebServer gives you a real socket-level test double instead of mocking at the OkHttpClient interface, which catches bugs that interface mocks never would.
The deliberate refusal to support 'invalid' configurations (no GET with body, no pluggable cache interface) means that when you're stuck talking to a server that doesn't follow spec, OkHttp won't bend and you're stuck wrapping or forking. Maven users hit a real footgun: the KMP packaging means the plain `okhttp` artifact resolves empty, forcing manual selection between `okhttp-jvm`/`okhttp-android` and BOM version juggling that Gradle users never see. MockWebServer is explicitly declared not actively developed for new features, so anyone building serious HTTP test tooling on it is building on a library the maintainers have told you to outgrow. Android support starts at API 21, which still excludes a meaningful tail of real-world devices in some markets.