bad requests for/ts sometimes do not respond

[toshbrown]

For example

A GET request for /ts/foo instead of /ts/foo/latest will hang clients as will /ts/[key]/[any unsupoted string]

To repeat:

docker run -p 5555:5555 -p 5556:5556 -d --name zest --rm jptmoore/zest /app/zest/server.exe --secret-key-file example-server-key --enable-logging

run --network host -it jptmoore/zest /app/zest/client.exe --server-key 'vl6wu0A@XP?}Or/&BR#LSxn>A+}L)p44/W[wXL3<' --path '/ts/foo' --payload '{"name":"dave", "age":30}' --mode post

docker run --network host -it jptmoore/zest /app/zest/client.exe --server-key 'vl6wu0A@XP?}Or/&BR#LSxn>A+}L)p44/W[wXL3<' --path '/ts/foo' --mode get

[John P. T. Moore]

Yes, there is no error handling on incorrect paths yet. Will add that shortly.

I will start a todo issue list soon with all these.

[John P. T. Moore]

ACKing with bad request now.