MG-RAST/Shock

Bad routes incorrectly resolve to good routes, rather than returning 404 errors

Closed this issue · 1 comments

The following routes incorrectly resolve to nodes:

GET /nodeqqq resolves to /node
GET /foobar resolves to /

This is particularly insidious if you mistakenly do:

GET /nodes/{id}

Which resolves to the collection resource for /node.

I need to either replace the goweb framework or fix it. I'm quite sure why its route matching behaves like this.