Redirect trailing slashes

[trestletech]

Consider Flask's approach:

@app.route('/projects/')
def projects():
    return 'The project page'

@app.route('/about')
def about():
    return 'The about page'

Though they look rather similar, they differ in their use of the trailing slash in the URL definition. In the first case, the canonical URL for the projects endpoint has a trailing slash. In that sense, it is similar to a folder on a filesystem. Accessing it without a trailing slash will cause Flask to redirect to the canonical URL with the trailing slash.

In the second case, however, the URL is defined without a trailing slash, rather like the pathname of a file on UNIX-like systems. Accessing the URL with a trailing slash will produce a 404 “Not Found” error.

This behavior allows relative URLs to continue working even if the trailing slash is omitted, consistent with how Apache and other servers work. Also, the URLs will stay unique, which helps search engines avoid indexing the same page twice.

[layik]

Hi @trestletech

Is this affecting dynamic routes too? Case is this:
endpoing = /test/<p:double>
IF we then curl /test that is a 404. Whilst curl /test/ would be fine.

Or is this something else?

Thanks

[layik]

or as I update to 0.4.6 things may be slightly different.

[schloerke]

Perfect Example: #481 (comment)

[schloerke]

As much as I am against this, there is prior art with apache. Maybe we can make it opt-in...