recently I've installed ORDS 188.8.131.52.18.02 and migrated my REST Webservices based on Apex 4.2
In these REST Webservices I've used the pseudo HTTP headers X-APEX-STATUS-CODE, X-APEX-METHOD and X-APEX-PATH
Unfortunately these won't work anymore in the migrated REST Webservices in the new ORDS 184.108.40.206.18.02.
How can I set, if possible, a custom HTTP status code?
It has to be set on a GET response.
The result of my REST pl/sql webservice is an error json object but with a custom http status code. Eg. 422.
Refer the following related threads:
- Restful post with X-APEX-STATUS-CODE parameter
- How to return 404 when entity not found?
It looks like this a bug in SQL Developer Version 220.127.116.11.59 when using ORDS 18.104.22.168.18.02.
When I create a new webservice GET handler it's not possible to create a parameter with Access Method OUT and source type HTTP HEADER.
This was/is working fine when using ORDS 22.214.171.1249.08.09
I'll post this issue in the SQL Developer forum.