Currently the delivery returns a 500 error code when it should return a 4** type error code when the client is attempting to reference a delivery endpoint or entity that does not exist.
Also, the response should not mention the RESTEASY library.
It also seems strange that this results in an exception in the log - is this desired behaviour?

To reproduce missing resource:
Request: http://localhost:8080/magnoliaAuthor/.rest/delivery/fdjsk

Result:
500 response code.
Response body: "RESTEASY003210: Could not find resource for full path: http://localhost:8080/magnoliaAuthor/.rest/delivery/fdjsk"
Exception and stack trace in log
The system should not return RESTEASY in a response as this is an implementation detail and should not be exposed to clients.

To reproduce missing entity:
Request: localhost:8080/magnoliaAuthor/.rest/delivery/tours/v1/magnolia-travels/A-Taste-of-Malaysia2

Result
500 response code
Response body: /magnolia-travels/A-Taste-of-Malaysia2
Exception and stack trace in log

—
In general 4** response codes should be used whenever the client makes an error in the request, and 500 should be used when the server/system is malfunctioning / overloaded.