Hey.

When looking at the ambiguities in the documentation for MergeSlashes:
  https://bz.apache.org/bugzilla/show_bug.cgi?id=65073#c1
I've noted that this seems to be more severely broken.

AFAIU before MergeSlashes was added it used to be like that:
- LocationMatch doesn't merge multiple slashes, so one must literally match them in the pattern, or e.g. use something like /+

- Location (non-regex) does merge multiple slashes, so a patter like "/foo/bar" will work for a request for "/foo//bar", too.


But it seems this is no longer the case with either MergeSlashes On or Off.

If set On, it work for:
 <Location "/xx/yy">
 request to "/xx/yy"  => match
 request to "/xx//yy" => match
but on can no longer literally match //:
 <LocationMatch "^/xx//yy$">
 request to "/xx/yy"  => no match
 request to "/xx//yy" => no match

If set Off, one can literally match //:
 <LocationMatch "^/xx//yy$">
 request to "/xx/yy"  => no match
 request to "/xx//yy" => match
but then the folding with Location (non-regex) is broken:
 <Location "/xx/yy">
 request to "/xx/yy"  => match
 request to "/xx//yy" => no match


Cheers,
Chris.