Brightspot CMS User Guide

URLs and trailing slashes


Brightspot assigns permalinks to assets, and those permalinks most often have no trailing slash. For example, an asset with the title Breakfast has a permalink /breakfast, and its URL is http://example.com/breakfast.

Visitors may mistakenly request URLs with a trailing slash. For example, you have an asset with the URL http://example.com/breakfast. To view that asset, a visitor mistakenly requests the non-existent URL http://example.com/breakfast/, and receives an error 404.

In rare cases, a permalink may have a trailing slash. For example, an asset with the title Lunch has a permalink /lunch/, and its URL is http://example.com/lunch/. To view that asset, a visitor may mistakenly request the non-existent URL http://example.com/lunch, and receive an error 404.

(When a permalink ends with a trailing slash, Brightspot internally appends index to the permalink. In this example, the permalink is /lunch/, and Brightspot internally stores the permalink as /lunch/index.)

You can configure Brightspot to append or remove trailing slashes so that visitors receive their intended assets—not an error 404.

Previous Topic
Adding wildcard URLs and redirects
Next Topic
Configuring trailing slash behavior
Was this topic helpful?
Thanks for your feedback.
The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

Content types
Modules
Landing pages
Everything you need to manage and administer content within Brightspot CMS.

Dashboards
Publishing
Workflows
Admin configurations
A guide for installing, supporting and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
Images
A guide for configuring different integrations to support a multitude of use cases.

Google Analytics
Shopify
Apple News