Use Query Parameters for Page DID Routing to Support DID Name Slashes
@maany is already working on this.
Since Jun 20, 2025.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 36
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 7
Description
Description
... continuation of work done in #548,
Switch from using path parameters to query parameters for representing Page DIDs. Query parameters are not subject to the same normalization rules and allow slashes to be preserved without encoding the structure.
From
/did/scope/name
To
/did?scope=belle&name=/detector/CAF/reprocessing/proc16_chunk2/b
Motivation
The current implementation URL-encodes DID names and uses path parameters for routing. In Issue #560, a catch-all route in Next.js ([...did]) was proposed to capture full DID paths from the URL. While this worked for many cases, it fails when DID names begin with a leading slash, as the browser and Next.js normalize the path and remove the extra slash (e.g., /did/scope//name becomes /did/scope/name).
This results in incorrect parsing of the DID and breaks expected behavior.
Change
No response
Additional Information
- The Rucio API needs to be changed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.