Loading...

XML

Word

Printable

Requests within the REST prefix that don't match any REST route will be routed with legacy, and get a 404 that isn't REST aware at all.

Make sure that any request within /api/ezp/v2 will be a proper 404, in the requested format (JSON or XML).

is duplicated by

EZP-22826 Regression: 404 errors within the REST prefix should be valid REST 404

testing discovered

EZP-21299 REST Exceptions with code / previous arguments generate a 500 error

EZP-21301 REST 404 catch-all prevent from extending the REST API

links to

PR #453

Closed

100%

Estimated:

Not Specified

Remaining:

30m

Logged:

Include sub-tasks