Removing trailing slashes example (Redirects)

[jamesmacwhite]

The Craft Cloud redirect doc currently provides this example:

redirects:
  - pattern:
      pathname: '/:noSlashes+'
    destination: '/{matches.pathname.groups.noSlashes}/'
    status: 301

I believe this adds a trailing slash to all URLs which typically Craft at the application level can do, what is the correct reverse logic to always trim trailing slashes? This would be great for redirection purposes where an old path like:

/example/page/

Would be automatically redirected:

/example/page

And if an redirect rule from something like Retour existed that would be matched but only for non-trailing slash variant

[timkelty]

@jamesmacwhite redirecting to a trimmed trailing slash is exactly the same, but without a trailing slash:

  - pattern:
      pathname: '/:noSlashes+'
    destination: '/{matches.pathname.groups.noSlashes}'
    status: 301

Because of how URLPattern's pathname matching works, the pathname: '/:noSlashes+' will match /all/the/segments/but/no/trailing/slash, so we just need to reference the match and include the trailing slash or not.

Proably a good idea to include both examples in our docs, though. /cc @AugustMiller

[jamesmacwhite]

• pattern:
  pathname: '/:noSlashes+/'
  destination: '/{matches.pathname.groups.noSlashes}{request.url.search}{request.url.hash}'
  status: 301

Thanks for this. However, I still don't see the rule working I'm afraid!

I've applied this redirect and deployed to Craft Cloud, confirmed the redirect rule is picked up by the deployment process (3 redirect rules total, two non-www to www rules for our custom domains and the rule below)

- pattern:
      pathname: '/:noSlashes+/'
    destination: '/{matches.pathname.groups.noSlashes}{request.url.search}{request.url.hash}'
    status: 301

However when testing in browser and with Curl, the response is a 404 not a 301 for the trailing slash request.

curl -Is "https://staging.nottinghamcollege.ac.uk/foo/bar/?baz=qux"
HTTP/2 404
date: Sat, 26 Jul 2025 11:01:39 GMT
content-type: text/html; charset=UTF-8
server: cloudflare
cf-ray: 965366759e0563b0-LHR
cf-cache-status: MISS
cache-control: no-cache, no-store, must-revalidate
strict-transport-security: max-age=15552000; includeSubDomains
vary: Accept-Encoding
via: id=161ca4c7;timestamp=2025-07-15T20:34:07.253091Z gateway
pragma: no-cache
dev-mode: 1
origin-cf-cache-status: MISS
origin-cf-ray: 96536675c0df63b0-LHR
x-amzn-requestid: 010edb75-fff4-4853-9a97-f06dd500ad9b
x-amzn-trace-id: Root=1-6884b592-3b1f59c651929d4d6b649e9e;Parent=36b7b686b645dbd5;Sampled=0;Lineage=1:fd3b1ae4:0
x-robots-tag: none
set-cookie: __cf_bm=fwXwfHQ.91iVKudL_zQyZPn_u4z_9xU7fvC7hygCPTQ-1753527699-1.0.1.1-FgxPVa3_KwWhkb3uLE2QolAafazHV1hCf855ikjFHOV8CsUcNhj7fOwu_MAr7l.Fr.zUOhTf0XDCU9BX02R5QIoH9YoqWWwrcMrDplb.BzU; path=/; expires=Sat, 26-Jul-25 11:31:39 GMT; domain=.staging.nottinghamcollege.ac.uk; HttpOnly; Secure; SameSite=None
alt-svc: h3=":443"; ma=86400

Even testing a valid path e.g. https://staging.nottinghamcollege.ac.uk/about-us/ the trailing slash is not removed.

[timkelty]

Check your YAML indentation – I think you have an invalid rule (we need to expose that in the build logs)

[jamesmacwhite]

Ah, thanks for being my eyes! Yes, it is the YAML indents. Copy and pasting doesn't always maintain them.

The build logs currently don't flag it, it sees 3 redirects, but I'd imagine that's because it knows there's 3 array items in the redirects key but isn't providing anything else currently.

Potential side quest, perhaps having a schema for the craft-cloud.yaml file, to allow IDE's like PHPStorm to validate the structure before committing would be something useful. I did the original work for the DDEV schema: ddev/ddev@0265ac7

I think there could be an opportunity for a schema for craft-cloud.yaml so you can IDE autocompletion/validation before you've committed.

Additional logs on invalid YAML would be nice in the builder though!

[timkelty]

Having a published schema is a lovely idea!
Would you mind logging a FR for it? https://github.com/craftcms/cloud/discussions/new?category=feature-requests-enhancements

[jamesmacwhite]

Will do! Redirect rule working great on our staging. Thank you!

For completeness, created as: #100