From b7fedf3aa37da0a18b44fc452ba1a48c554513ae Mon Sep 17 00:00:00 2001 From: Joe Orton Date: Tue, 16 Apr 2019 08:13:46 +0000 Subject: Transforms. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1857629 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html.en | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) (limited to 'docs/manual/mod/core.html.en') diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 35eccf570a..d837c458b7 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -100,6 +100,7 @@ available
  • MaxRangeOverlaps
  • MaxRangeReversals
  • MaxRanges
    • +
  • MergeSlashes
  • MergeTrailers
  • Mutex
  • NameVirtualHost
    • @@ -3619,6 +3620,32 @@ resource server is willing to satisfy. + +
    top
    +

    MergeSlashes Directive

    + + + + + + + + +
    Description:Controls whether the server merges consecutive slashes in URLs. +
    Syntax:MergeSlashes ON|OFF
    Default:MergeSlashes ON
    Context:server config, virtual host
    Status:Core
    Module:core
    Compatibility:Added in 2.5.1
    +

    By default, the server merges (or collapses) multiple consecutive slash + ('/') characters in the path component of the request URL.

    + +

    When mapping URL's to the filesystem, these multiple slashes are not + significant. However, URL's handled other ways, such as by CGI or proxy, + might prefer to retain the significance of multiple consecutive slashes. + In these cases MergeSlashes can be set to + OFF to retain the multiple consecutive slashes. In these + configurations, regular expressions used in the configuration file that match + the path component of the URL (LocationMatch, + RewriteRule, ...) need to take into account multiple + consecutive slashes.

    +
    top

    MergeTrailers Directive

    -- cgit v1.2.3