Accurids redirection component allows configuring URL rewriting rules to resolve persistent identifiers so that users and machines can obtain information through a simple HTTP lookup. The target of the redirection can point to other applications or to Accurids itself when the target application is temporarily unavailable or returns not found response code (HTTP 404 code). Redirections can be managed by eligible users (contributors and admins).
To create a redirection, select ID Management in the left sidebar and click on the REDIRECTION tab. A list of existing redirections is shown. Click plus in the upper right corner and enter the following mandatory information in the presented form:
- Name: A descriptive title for the redirection
- Detection Pattern: URI pattern that must be matched to trigger the request redirection
- Target URL Pattern: URI pattern used to locate and resolve a resource. For further customization, the following rewriting variables can be used for the Target URL Pattern parameter.
View and Modify Redirections
To view details on an existing redirection, click the eye icon next to it. A details page will be shown that contains details and status (active or inactive) of the redirection.
All aspects of the redirection can be modified. It is also possible to activate/deactivate redirection to stop the resolution mechanism by clicking on the activate icon.
The audit trail information can be viewed by clicking on the Audit Trail icon that will open a window with a detailed log of all performed actions including:
- Modified date
- Updated fields
- Modified by
Redirection through URL Re-Writing
For further customization, the following rewriting variables can be used for the Target URL Pattern parameter (
https://pid.example.com/demo/ST00001 is used as an example):
|$URI||The full PID (request)||https://pid.example.com/demo/ST00001|
|$namespace||The substring of the PID up to the last "#" or "/"||https://pid.example.com/demo|
|$host||A host subcomponent, consisting of either a registered name (including but not limited to a hostname), or an IP address||pid.example.com|
|$path[n]||A sequence of path segments separated by a slash (/) between host and local ID||path = demo|
|$localId||A substring which comes after the last "#" or "/"||ST00001|
The following table provides examples for the
https://pid.example.com/demo/ST00001 request with a detection pattern like
https://pid.example.com/demo and different target URL patterns:
|Detection Pattern||Target URL Pattern||Redirection Location|