roaster
roaster copied to clipboard
eeditiones
Open API Router for eXist
In roaster 1.0.0 when an error gets triggered, this is always json and in rare cases xml regardless of the Accept header in the client request. This is due to...
fixes #73 If the error raised does neither have a description nor a value it will now return "No description provided."
Please have a look at the documentation for the new feature: https://github.com/eeditiones/roaster/blob/3b0ab4e867a21683bb00b93ab0be7809b6200887/doc/cookie-auth.md **FEATURES** - allow and encourage custom login route handlers - read user name and login from any body...
- type cast of values in the array (previously all parameters in the array were treated as string) - converts values of the parameter with **form**=`style` and **explode**=`false` (values separated...
This is just the first one that comes to my mind, there is likely more (bad request, ok, ...) `roaster:server-error($data)` would be equivalent to `roaster:response(500, $data)`
As per RFC 9110, section 15.5.6, if a `405 Method Not Allowed` is returned, this response MUST have an `Allow` header listing all permitted methods.
Assume a basic API with: ```yaml … paths: /projects: get: … post: … … ``` A request of `OPTIONS http://localhost:8080/exist/apps/…/projects` currently returns ``` HTTP/1.1 200 OK … Allow: GET, HEAD,...
Currently, on POST at least, if a "Content-Type" header is sent with a type that is not declared in the spec, a `400 Bad Request` is returned (from: body.xqm:130) This...
This sentence should maybe deleted to not encourage wrong OpenAPI usage which requires operationId to be unique.
