From 920d2b68913979fd0e1caf03aad75e8abbc1f7ac Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 30 Sep 2009 04:43:37 +0000 Subject: Fix. --- docs/narr/urldispatch.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst index 3be117933..71eaf3341 100644 --- a/docs/narr/urldispatch.rst +++ b/docs/narr/urldispatch.rst @@ -572,14 +572,14 @@ your route configuration is looks like so, and the If a request enters the application with the ``PATH_INFO`` value of ``/no_slash``, the first route will match. If a request enters the -application with the ``PATH_INFO`` value of ``/no_slash``, *no* route +application with the ``PATH_INFO`` value of ``/no_slash/``, *no* route will match, and the slash-appending "not found" view will *not* find a matching route with an appended slash. -If a request enters the application with the ``PATH_INFO`` value of -``/has_slash/``, the second route will match. If a request enters the -application with the ``PATH_INFO`` value of ``/has_slash``, a route -*will* be found by the slash appending notfound view. An HTTP +However, if a request enters the application with the ``PATH_INFO`` +value of ``/has_slash/``, the second route will match. If a request +enters the application with the ``PATH_INFO`` value of ``/has_slash``, +a route *will* be found by the slash appending notfound view. An HTTP redirect to ``/has_slash/`` will be returned to the user's browser. Note that this will *lose* ``POST`` data information (turning it into -- cgit v1.2.3