Support pathing

[jackkav]

motivation: as a user i might like to mock an api surface with multiple endpoints and responses a varying paths.

problem: mockbin generates an id on bin creation that is used for the path so paths that follow the id are ignored or unmatched by express.

aim: the following could all return different responses
bin/123-123-123-123/route-a
bin/123-123-123-123/route-b
bin/123-123-123-123/route-b/route-1

approach

• include the path in the redis key
• avoids making redis values into arrays of responses per path
• use the url and a put method to indicate path to match

NOTE: you must first initialise a a mock response with a PUT request to a url you would like to mock with a HAR body of the response

to do

• rotate log, view, sample endpoint paths to avoid conflict
  • alternatively since we only use log run and update, we could create a new route

Questions:

• what should happen when and endpoint hasn't been initialised?

future work

• validation, bad input errors,
  • do this later when we understand usage better
• sanitization: trailing slashes, query params, max key size, perf implications,
  • do this later when we understand usage better
• support mocked methods besides GET, eg POST, PUT, DELETE
  • will mean using the request body to configure the path rather than the url

[filfreire]

LGTM, tested locally. We found edge-case with trying to use bins directly on the mockbin ui when someone hits an endpoint that has not been initialised. Up for questions, but I think we can merge.