An HTTP & HTTP/2 Server and Client library for Scala.
A server is built from a plain function accepting an HTTP request and eventually giving back an HTTP response. The computation is wrapped into an effect and can handle pure & impure and synchronous & asynchronous scenarios. Requests and responses are just HTTP metadata along with a lazy content body based on fs2, making it easy to handle streaming scenarios if needed. For additional convenience, the library provides content encoders and decoders for the common scala types. Clients and Servers share the same API and the same concepts, making it easy to compose them. SSL is supported on both sides.
// Let's start an HTTP server
Server.listen(8888) {
case GET at "/hello" =>
Ok("Hello World!")
case _ =>
NotFound
}
// Let's connect with an HTTP client
Client.runSync(Get("http://localhost:8888/hello")) { res =>
res.readAs[String].map { contentBody =>
println(s"Received: $contentBody")
}
}HTTP/2 is supported on both Server and Client side. If SSL is enabled, the protocol negociation is done using ALPN. On plain connections however HTTP/2 is only supported with prior knowledge (clear text upgrade from HTTP/1.1 to HTTP/2 is ignored). Because of ALPN, HTTP/2 support over SSL requires running on Java 9 (Running on Java 8 is still possible but you need to replace the default Java TLS implementation; see http://www.eclipse.org/jetty/documentation/current/alpn-chapter.html#alpn-starting).
The library is cross-built for Scala 2.11 and Scala 2.12.
The core module to use is "com.criteo.lolhttp" %% "lolhttp" % "0.8.0".
There are also 2 optional companion libraries:
"com.criteo.lolhttp" %% "loljson" % "0.8.0", provides integration with the circe JSON library."com.criteo.lolhttp" %% "lolhtml" % "0.8.0", provides minimal HTML templating.
The API documentation is the main reference.
If you never used cats effects before, you should start by having a quick look at it. Service Responses must be wrapped
into an IO (although there is an implicit conversion translating Response into a pure IO if needed). Also consuming the underlying content stream data is an effect. For asynchronous scenarios you have to deal with asynchronous effects, unless you prefer working with Future and wrapping it at the end using IO.fromFuture.
If you need to access the underlying content stream, you should first have a look a the fs2 documentation to understand the basics.
For those who prefer documentation by example, you can also follow these hands-on introductions:
- Hello world!
- Serving files from classpath.
- A Github API client.
- A JSON web service.
- Reading large request streams.
- A simple reverse proxy.
- An HTTP/2 server.
This project is licensed under the Apache 2.0 license.
Copyright © Criteo, 2017.