journey
journey copied to clipboard
cloudhead
liberal JSON-only HTTP request routing for node.
https://github.com/cloudhead/journey/blob/master/lib/journey.js#L382 This means that you cannot return files, it would be best to fix this and then expose the initial response object so streams can be used.
When I was using the journey router, there were times when I wanted to return pure string responses instead of json. An example would be returning some html. This commit...
If a buffer is returned from a route, currently Journey will error on the line, as byteLength is expecting a string. ``` Buffer.byteLength(outcome.body);``` Seeing as converting a Buffer to JSON...
Patch for supporting passing numbers as strings. For example "0001" is treated as string instead of 1. Also added seccond parameter to parseInt for setting base 10 for convertions instead...
The error 401 error must return the header "WWW-Authenticate" for certain browser to send back the "authentication" header. I also incremented the version and added contributors from previously closed pull...
I have a regex route containing the capture group `(.+)` (matching everything). This works as expected most of the time and I can access the matched group in the third...
In the documentation it says: "How about a POST request, with form data, or JSON? Same thing, journey will parse the data, and pass it as the last argument to...
It seems it's currently not impossible to place the functions handling the routes outside of the closure, if they need access to the parent context, say things like a database...
