Re: svn commit: r1762651 - /httpd/httpd/trunk/docs/manual/rewrite/flags.xml

[Yann Ylavic <yl...@gmail.com>]

On Wed, Sep 28, 2016 at 3:12 PM,  <rb...@apache.org> wrote:
> Author: rbowen
> Date: Wed Sep 28 13:12:26 2016
> New Revision: 1762651
>
> URL: http://svn.apache.org/viewvc?rev=1762651&view=rev
> Log:
> Actually show the example of how to do this.
>
> Modified:
>     httpd/httpd/trunk/docs/manual/rewrite/flags.xml
>
> Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.xml
> URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.xml?rev=1762651&r1=1762650&r2=1762651&view=diff
> ==============================================================================
> --- httpd/httpd/trunk/docs/manual/rewrite/flags.xml (original)
> +++ httpd/httpd/trunk/docs/manual/rewrite/flags.xml Wed Sep 28 13:12:26 2016
> @@ -94,6 +94,10 @@ isn't a valid URL, and so would be encod
>  before being passed on to the output URL, resulting in a correct mapping to
>  <code>/search.php?term=x%20%26%20y%2Fz</code>.</p>
>
> +<highlight language="config">
> +RewriteRule "^search/(.*)$" "/search.php?term=$1" [B,PT]
> +</highlight>
> +
>  <p>Note that you may also need to set <directive
>  module="core">AllowEncodedSlashes</directive> to <code>On</code> to get this
>  particular example to work, as httpd does not allow encoded slashes in URLs, and

Shouldn't we recommend AllowEncodedSlashes "NoDecode" here (instead of "On")?
It should work the same for this case, but is somehow safer.

Regards,
Yann.