Take for example the following two routes.
app = Flask(__name__)
@app.route("/somewhere")
def no_trailing_slash():
#case one
@app.route("/someplace/")
def with_trailing_slash():
#case two
According to the docs the following is understood:
In case one, a request for the route
"/somewhere/"
will return a 404 response."/somewhere"
is valid.In case two,
"/someplace/"
is valid and"/someplace"
will redirect to"/someplace/"
The behavior I would like to see is the 'inverse' of the case two behavior. e.g. "/someplace/"
will redirect to "/someplace"
rather than the other way around. Is there a way to define a route to take on this behavior?
From my understanding, strict_slashes=False
can be set on the route to get effectively the same behavior of case two in case one, but what I'd like to do is get the redirect behavior to always redirect to the URL without the trailing slash.
One solution I've thought of using would be using an error handler for 404's, something like this. (Not sure if this would even work)
@app.errorhandler(404)
def not_found(e):
if request.path.endswith("/") and request.path[:-1] in all_endpoints:
return redirect(request.path[:-1]), 302
return render_template("404.html"), 404
But I'm wondering if there's a better solution, like a drop-in app configuration of some sort, similar to strict_slashes=False
that I can apply globally. Maybe a blueprint or url rule?
/somplace/
redirect to/someplace
? – BusturdustDEBUG=True
in your Flask config the trailing spaces are not redirected but whenDEBUG=False
then it is redirected. – kiran.koduruapp.debug = True
it doesn't appear to take in the gevent WSGI environment. I'm sure there's a way to solve that problem, but is another question and as explained, probably not an applicable solution to this question, for a production environment. – sytech