Securing a site that uses mod_rewrite

Fournier, Danny G Danny.Fournier at dfo-mpo.gc.ca
Wed May 15 13:43:38 EDT 2013


> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 15 May 2013 14:38:57 +0000
> From: "Cantor, Scott" <cantor.2 at osu.edu>
> Subject: Re: Securing a site that uses mod_rewrite
> To: Shib Users <users at shibboleth.net>
> Message-ID:
> 	<BA63CEAE152A7742B854C678D9491383750FD0A2 at CIO-KRC-
> D1MBX01.osuad.osu.edu>
> 
> Content-Type: text/plain; charset="us-ascii"
> 
> On 5/15/13 10:30 AM, "Fournier, Danny G" <Danny.Fournier at dfo-
> mpo.gc.ca>
> wrote:
> 
> >I'm trying to access the status page using the following URL (which
> >matches the handlerURL of my configuration):
> >my.domain.com/somepath/00101/esas.sso/status.
> 
> Well, it's Status, not status, so that's one problem.
> 
> But I would strongly recommend not changing the handler URL, and just
> exclude that tree from the rewrite rules.
> 
> -- Scott
> 

Thanks Scott.

I added the following condition for the rewrites:
RewriteCond 	%{REQUEST_URI}
!^/somepath/00101/esas.sso/.*$

It seems to have done the trick.



More information about the users mailing list