Raxx 0.14.8 released
Configuration option allows extra statuses to be added.
e.g.
# config/config.exs
config :raxx,
:extra_statuses, [{418, "Im A Teapot"}]
# iex -S mix
Raxx.response(:im_a_teaport)
# => %{status: 418, ...}
Crowdhailer
Creator of Raxx
1
Crowdhailer
Creator of Raxx
Raxx 0.14.10 released
Default instructional page is now server with status 404 (was 200). Helps reduce false positive in test cases.
1
Crowdhailer
Creator of Raxx
Raxx 0.14.12 released, including helper for browser redirection.
From the changelog
Added
Raxx.get_header/2for fetching a single header value from a request/response.Raxx.redirect/2will generate a redirect response directing browser to another url.- Header values checked for forbidden charachters using
Raxx.set_header/3. Raxx.get_header/3return fallback value if required header is not set.
3
Crowdhailer
Creator of Raxx
Basic authentication and Sessions added in 0.14.13 release.
This release adds two new modules to the core Raxx project
- Raxx.BasicAuth Add protection to a Raxx application using Basic Authentication.
- Raxx.Session.SignedCookie Use signed cookies to store the session of a client.
3
Crowdhailer
Creator of Raxx
Secure browser headers and request_id middleware added in 0.14.14
Added
Raxx.set_secure_browser_headers/1Adds a collection of useful headers when responding to a browser.Raxx.delete_header/2delete a header from request or response.Raxx.RequestIDassign a request id to every request handled by an application
2
Crowdhailer
Creator of Raxx
major release 0.15.0.
%Raxx.Request{} now has query strings as a binary, to access the parsed query use Raxx.fetch_query/1
This allows consumers to access the raw query to handle parsing in different ways, such as accepting multiple values per key or implementing nested queries. It is also more performant for servers because they do not parse queries that are not used
1
Qqwy
TypeCheck Core Team
First of all, let me say that I think it is a great idea that other types of solutions besides Plug are being explored. I think the message-passing model could work really well, and I am very interested to see how it evolves.
However, I am not really happy with how the middlewares currently work, since they ‘decorate’ the original handle_xxxx call with their own wrapper at compile time which may result in performant code, but it makes the middleware code itself quite hard to read.
And as a secondary issue, changes in one of the middlewares will probably result in Elixir having to re-compile a lot of your application since these are compile-time behaviours that will live at the core of your webserver. This was also a problem in Plug that was recently mitigated by opting out of the compile-time consolidation-optimization in the development environment, but this would not be possible in your current implementation because of the way middlewares are currently implemented.
Of course, you have more freedom when you do not restrict middlewares to be composed in a method very similar to function composition (Which is what Plug does; plug modules are basically functions with an optional prior initialization step).
I think the idea to model client<->server communication as message-passing is a really smart one, but maybe the middlewares can work with that without having to become macro-heavy creatures. Writing middlewares as modules that contain some pattern-matches for the handle_request calls that might decide between:
- returning whatever they want and stop the passing-through to the next middleware.
- indicating that the request should pass through to the next middleware.
Then, secretly the middleware wrapper would call these in turn whenever the ‘passthrough’ result was returned. And maybe it would even be possible to optionally use some AST remolding to make it faster by transforming it optionally into a large set of function-clauses after all. But that would make the middleware modules themselves a lot easier to read and maintain.
2
Crowdhailer
Creator of Raxx
I am certainly interested in exploring solutions like this. It is something that has come up several times in the slack channel. For the moment I am exploring just not using middleware.
Instead of
use Raxx.Session
# later
Raxx.get_session(request)
I have something that just extracts the session when asked
Raxx.Session.extract(request)
1
Qqwy
TypeCheck Core Team
So you’d explicitly add those statements to your server?
Interesting idea. Is it abstractable? 
0
Crowdhailer
Creator of Raxx
Not sure quite what you mean. So far it’s not been to bad because in many cases middleware is a layer of indirection. replacing the two or three things that would have been sensible middleware admittedly costs a few lines but it is ludicrously explicit, easy to understand and test.
1