On Thu, 30 Apr 2015, Yann Ylavic wrote:
On Thu, Apr 30, 2015 at 2:57 PM, Jim Riggs <apache-li...@riggs.me> wrote:
Thanks, Yann. I remember looking at this code before. The question remains, though: Is it
currently "wrong"?
Does it need to be "fixed", or was this distinction made intentionally?
Is there a specific use case that requires the regex-matching directives to not
get slash-normalized URIs?
I would like it to be fixed, non leading "/+" is equivalent to "/",
this would break very few (if any) cases IMHO, and may even unbreak
more ones .
+1
I would expect Location and LocationMatch using the same uri for
comparison. I would actually go so far as the current state might
warrant a CVE for being a hidden security risk that might cause
inadvertent information exposure.
If someone really wants to have the "raw" uri for some reason I guess
they can use <If> and a suitable expr?
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | ni...@acc.umu.se
---------------------------------------------------------------------------
I! finally! learned! to! punctuate! Kirk's! sentences!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
