How to write a custom middleware
View SourceA middleware runs before or after every handler in a stack: auth, CORS, rate limiting, feature flags, changes to the request. You need one when the same behaviour applies to many handlers and you do not want to repeat it in each one.
Implement the behaviour
Implement the livery_middleware behaviour. One callback:
call(Req, Next, State) -> Resp.
-module(my_cors).
-behaviour(livery_middleware).
-export([call/3]).
call(Req, Next, #{origins := Allowed} = State) ->
case livery_req:header(<<"origin">>, Req) of
undefined ->
Next(Req);
Origin ->
case lists:member(Origin, Allowed) of
true ->
Resp = Next(Req),
livery_resp:with_header(
<<"access-control-allow-origin">>, Origin, Resp);
false ->
livery_resp:text(403, <<"origin not allowed">>)
end
end.Add it to a stack as {my_cors, #{origins => [...]}}.
Use the sugar helpers
For simple cases, these helpers build the middleware for you, so you do not need a module of your own:
%% Mutate the request, then continue.
livery_middleware:before(fun(R) ->
livery_req:set_meta(start, erlang:monotonic_time(), R)
end).
%% Mutate the response on the way out.
livery_middleware:after_response(fun(R) ->
livery_resp:with_header(<<"X-Server">>, <<"livery">>, R)
end).
%% Catch downstream exceptions and turn them into a response.
livery_middleware:wrap(fun(Class, Reason, _Stack) ->
livery_resp:text(500,
iolist_to_binary(io_lib:format("~p: ~p", [Class, Reason])))
end).Pick a shape
A middleware takes one of three shapes:
- Pass-through. Change the request or the response. Always call
Next. Example:livery_request_id,livery_access_log. - Short-circuit. Skip
Nextand return a response directly. Example: failed auth, a rate limit reached. - Wrapper. Run
Nextinsidetry/catchor a monitor. Example:livery_middleware:wrap,livery_timeout.
Store state on the request
Use livery_req:set_meta/3 to pass values from a middleware to the
handler:
call(Req, Next, _State) ->
{ok, User} = verify(Req),
Next(livery_req:set_meta(user, User, Req)).The handler reads it back with livery_req:meta(user, Req).
Order the stack
The first entry in the stack list is outermost. Put auth before business logic. Put request id and error wrappers at the very top so every response carries them.
Test it
denies_when_origin_missing_test() ->
Cap = livery_test_adapter:run(
[{my_cors, #{origins => [<<"https://app">>]}}],
fun (_R) -> livery_resp:text(200, <<>>) end,
#{headers => [{<<"origin">>, <<"https://evil">>}]}),
?assertEqual(403, livery_test_adapter:status(Cap)).See also
- Tutorial: Compose a middleware stack
- Reference:
livery_middleware - Reference:
livery_request_id,livery_body_limit,livery_timeout,livery_access_log