Joel Bodenmann
Joel Bodenmann
Currently, `malloy::server::http::router_adaptor`'s `websocket()` and `http()` functions use a different style to log to the connection logger. This should be unified.
The `http::request` constructor accepting an rvalue of the underlying beast request currently parses cookies. However, this doesn't really make sense. We should only parse cookies when we really need them....
Add an interface to register mime-types. Something similar to how nginx configuration files allow for `http { types { } }` .
The HTTP server already implements connection `keep-alive`. The client has most pieces in place for this as well. However, the controller will create a new connection on every request. We...
As of today, `malloy::server::listener` binds starts to listen in the constructor. If the acceptor could not start listening (for example because the end-point is already in use), there is no...
As of today, everything related to forms is located in the `malloy::html` namespace. However, this doesn't make a lot of sense as everything implemented there is based on the HTTP...
As of today, `http::generator` provides some standard HTTP responses. These are mainly provided for convenience and are only used in very few places within the library itself. It might make...
The `malloy::html::form` class should perform check regarding all fields marked as `required` when parsing via `parse()`.
Currently, the cookie name for HTTP sessions is hard-coded in `malloy::http:;session::manager`. It might be desirable that a consuming application can override this.
Currently, properties that are used by both client and server (connections) such as the agent string and the body size limit are implemented separately in both the client and the...