Le 26/03/2019 à 22:52, Eric Covener a écrit :
# GET /authz_core/a/b/c//index.html HTTP/1.1\r\nHost:
merge-disabled\r\nConnection: close\r\n\r\n
# expected 200, got 403 for c// doesn't match locationmatch
not ok 7
# Test 7 got: "403" (t/apache/mergeslashes.t at line 73 fail #7)
> ># GET /authz_core/a/b/c//index.html HTTP/1.1\r\nHost:
> > merge-disabled\r\nConnection: close\r\n\r\n
> ># expected 200, got 403 for c// doesn't match locationmatch
> >not ok 7
> ># Test 7 got: "403" (t/apache/mergeslashes.t at line 73 fail #7)
> ># Expected: "200" (c//
Le 26/03/2019 à 09:16, Joe Orton a écrit :
On Tue, Mar 26, 2019 at 07:13:03AM +0100, Christophe JAILLET wrote:
Hi,
not related to this patch (I have the same output before it was applied),
but on my system, I get:
# SENDING to 127.0.0.1:8546
# GET /authz_core/a/b/c//index.html
On Tue, Mar 26, 2019 at 07:13:03AM +0100, Christophe JAILLET wrote:
> Hi,
>
> not related to this patch (I have the same output before it was applied),
> but on my system, I get:
>
> # SENDING to 127.0.0.1:8546
> # GET /authz_core/a/b/c//index.html HTTP/1.1\r\nHost:
>
Hi,
not related to this patch (I have the same output before it was
applied), but on my system, I get:
# SENDING to 127.0.0.1:8546
# GET /authz_core/a/b/c//index.html HTTP/1.1\r\nHost:
merge-disabled\r\nConnection: close\r\n\r\n
# expected 200, got 403 for c// doesn't match
