OpenSRF returns 200 status when calling APIs that don't exist

[Jason Boyer]

I believe all current versions do this.

If you use the html gateway to make an api call and there's no handler you will get an empty payload back with a 200 status. This is very misleading and can lead developers to think there's a problem with their params rather than the call itself or a service's public registration.

For example, calling something like open-ils.notfound should return a 404:
https://demo.evergreencatalog.com/osrf-gateway-v1?service=open-ils.notfound&method=ghost.like.swayze&param=%22Boo%22
But instead we get this:
{"payload":[],"status":200}

I don't think the actual http status should be 404 but OpenSRF certainly should use that status in this case.

There will need to be some care in how this is addressed since the Evergreen Version call:
https://demo.evergreencatalog.com/osrf-gateway-v1?service=open-ils.circ&method=opensrf.open-ils.system.ils_version
isn't actually published in any service.

[Bill Erickson (berick)]

A PR:

https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/berick/lp1928339-osrf-gateway-not-found-status