ORDS, SODA & JSON in the Database

I have read other posts:

• Terminating /
• Is ORDS requirement for trailing slash a Bug?

but I think there is some inconsistency in the trailing slash requirement.

This wat I want:

1. collection query employees
   URI: ..../ords/employees/
2. collection query item employees/:id
   URI: ..../ords/employees/:id
3. Post
   URI: ..../ords/employees (no trailing slash here)

This works although I think the trailing slash for the collection query should not be necessary.

But if you omit it in the definition then the links in the json results are not correct.

But ok, i can live with that, the endpoint ..../ords/employees (without the trailing slash als works).

The third requirement is a post request to:

URI: ..../ords/employees (without the trailing slash. With a trailing slash would be an odd requirement).

So I had to create another resource template.

In the post definition I want to use the X-ORDS-FORWARD header param to automatically include the result of ..../ords/employees/:id (resource 2., see above).

Whatever I try, I will always get a 401 (not authorized).

If I post to ..../ords/employees/ (with the slash) it works fine, but as I said, a strange requirement.

Any suggestions would be very much appreciated

Cheers Joep