This library lets you implement an HTTP server with handlers for each endpoint of a servant API, handling most of the boilerplate for you.
Getting started
We’ve written a tutorial guide that introduces the core types and features of servant. After this article, you should be able to write your first servant webservices, learning the rest from the haddocks’ examples.
Deprecate serveDirectory and introduce serveDirectoryFileServer,
serveDirectoryWebApp, serveDirectoryWebAppLookup, serveDirectoryEmbedded
and serveDirectoryWith which offer 4 default options and a more flexible
one for serving static files.
(#658)
DelayedIO is an instance of MonadResource, allowing safe resource handling.
(#622
, #674
, #675)
The Router type has been changed. Static router tables should now
be properly shared between requests, drastically increasing the
number of situations where servers will be able to route requests
efficiently. Functions layout and layoutWithContext have been
added to visualize the router layout for debugging purposes. Test
cases for expected router layouts have been added.
If an endpoint is discovered to have a non-matching “accept header”,
this is now a recoverable rather than a fatal failure, allowing
different endpoints for the same route, but with different content
types to be specified modularly.
Export throwError from module Servant
Add Handler type synonym
0.6.1
If servers use the BasicAuth combinator and receive requests with missing or
invalid credentials, the resulting error responses (401 and 403) could be
overwritten by subsequent alternative routes. Now BasicAuth uses FailFatal
and the error responses can’t be overwritten anymore.
0.6
Query parameters that can’t be parsed result in a 400 (was 404).
