Browse Source

expand explantion about default redirects

pull/2729/head
David Lord 7 years ago
parent
commit
5d00869aa5
No known key found for this signature in database
GPG Key ID: 7A1C87E3F5BC42A8
  1. 13
      docs/api.rst

13
docs/api.rst

@ -717,9 +717,18 @@ definition for a URL that accepts an optional page::
pass pass
This specifies that ``/users/`` will be the URL for page one and This specifies that ``/users/`` will be the URL for page one and
``/users/page/N`` will be the URL for page `N`. ``/users/page/N`` will be the URL for page ``N``.
Note: Underlying behaviour in Werkzeug redirect URLs containing a default value to its simpler form with a 301 redirect. If a URL contains a default value, it will be redirected to its simpler
form with a 301 redirect. In the above example, ``/users/page/1`` will
be redirected to ``/users/``. If your route handles ``GET`` and ``POST``
requests, make sure the default route only handles ``GET``, as redirects
can't preserve form data. ::
@app.route('/region/', defaults={'id': 1})
@app.route('/region/<id>', methods=['GET', 'POST'])
def region(id):
pass
Here are the parameters that :meth:`~flask.Flask.route` and Here are the parameters that :meth:`~flask.Flask.route` and
:meth:`~flask.Flask.add_url_rule` accept. The only difference is that :meth:`~flask.Flask.add_url_rule` accept. The only difference is that

Loading…
Cancel
Save