Problem that this fixes

With the current (2.0) REST API, there is no way to translate an URL alias into a location or content.

Specification

The locations list resource (/content/locations) already supports filtering on id and remoteId:

GET /api/ezp/v2/content/locations?remoteId=somelocationremoteid
GET /api/ezp/v2/content/locations?id=1234

It therefore makes sense that the location matching a URL aliases can be looked up the same way:

GET /api/ezp/v2/content/locations?urlAlias=Path/To-Content

The resource should behave as it does with the other arguments, or without any arguments, and return a reference to the matching location.

Tasks

• REST specification update
• Implementation
• Functional tests