Rule `/core/no-trailing-slash` uitbreiden (`//` ook uitsluiten)

[BvanRaaij]

ADR /core/no-trailing-slash geeft aan dat een URI niet op een / mag eindigen:

MUST NOT contain a trailing slash. When requesting a resource including a trailing slash, this MUST result in a 404 (not found) error response and not a redirect. This forces API consumers to use the correct [URI]

Ik wil voorstellen deze uit te breiden tot:

URL Paths MUST be normalized without empty path segments and trailing slashes:

You MUST NOT specify paths with duplicate or trailing slashes, e.g. .../v1/articles//comments or .../v1/articles/. As a consequence, you MUST NOT specify or use path variables with empty string values.

When requesting a resource including a trailing slash, this MUST result in a 404 Not Found error response and not in a redirect. This forces API consumers to use the correct URI.

This rule does not apply to the root resource (append / to the service root URL).

Dus: ook geen duplicate slashes toegestaan

[sanderke]

Bedankt voor de suggestie.

Voorstel om de regel algemener te maken:

- A URI MUST NOT contain a trailing slash.
+ A URI MUST NOT contain empty path segments.

- When requesting a resource including a trailing slash, this MUST result in a 404 (not found) error response and not a redirect.
+ When requesting a resource including a trailing slash or consecutive slashes, this MUST result in a 404 (not found) error response and not a redirect.

  This forces API consumers to use the correct URI.