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.