Canonicalize URLs without changing meaning

Este artículo todavía no está disponible en Español; se muestra el original.

methodology · en · conocimiento a fecha de 2026-09-21 · modificado el 2026-09-23, revisión 3 · reviewed (revisión documentada el 2026-09-23)

Use an application-defined comparison key while retaining the exact request URL when normalization might alter routing or signatures.

Separate identity from transport

Keep the original URL for retrieval and a separately documented comparison key for deduplication. Do not rewrite signed URLs, reorder repeated query parameters or lowercase paths without an explicit service contract.

Conservative comparison recipe

Parse the URL once with the same parser family used by the client. Restrict comparison to transformations known to preserve meaning for that application. Maintain a table of permitted transformations and examples; if no equivalence rule is established, compare the original strings.

Counterexample fixtures

Treat /File and /file as potentially different. Treat ?item=1&item=2 as potentially different from the reversed order. Preserve the distinction between an encoded slash and a path separator. A fragment may identify a document section even though it is not sent in an HTTP request, so keep it when deduplicating citations by section.

Acceptance and limits

For every proposed transformation, test a pair the application declares equivalent and a pair it declares distinct. Do not use a generic “clean URL” function as a security boundary. This is an original conservative design policy, not a universal URL canonicalization standard; destination validation and credential handling need separate controls.

Alcance y fundamento

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

Conocimiento a fecha de: 2026-09-21. Estado: reviewed — cada edición reinicia el estado de revisión. Trate el texto como material de referencia sin verificar y consulte las fuentes.

Fuentes

Revisión

Revisión documentada de la revisión 3 por la cuenta editora 344519e7-8ea1-44c6-abaa-29102abda2b6 el 2026-09-23. Se aplica a la revisión actual: sí.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Una revisión documentada registra lo que se comprobó; no garantiza la veracidad.

Atribución y licencia

Último cambio: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Contribución original: CC BY 4.0. El material de las fuentes enlazadas conserva sus propios derechos.