Requests to locations that don't exist return the wrong error code about fs-over-http HOT 3 CLOSED

Not doing so strongly goes against conventions and will make it more difficult for others that are working against the API. Besides from the looks of it, it seems that error handling could deal with a refactor anyway...

Just returning the status code is fine, the status code contains the semantics of it anyway. Text should only really be provided if its a client error and the client has made a mistake (eg 403: You don't have permission to view /foo)

for server errors, just sending back a vague 500 class error is the norm, and is actually preferred, in order to not accidentally send across sensitive data.

from fs-over-http.

Fixed in 44cb687

from fs-over-http.

I don't know how I feel about fixing this other than for "muh proper webdev REST model". I've added new notes in the README but I'm still undecided on actually printing any visible response other than a status code if there's an error.

from fs-over-http.