From: "Philip M. Gollucci" <[EMAIL PROTECTED]> > Octavian Rasnita wrote: > > Instead of using: > > > > <Location /> > > SetHandler perl-script > > PerlResponseHandler ModPerl::Testing > > </Location> > > > > I can use: > > > > <LocationMatch ^/$> > > SetHandler perl-script > > PerlResponseHandler ModPerl::Testing > > </LocationMatch> > Does that still for for example > http://google.com > vs > http://google.com/ > > -- > END
Yes it also handles that path (no-path) I heard that some browsers use to add the "/" after the location if it doesn't end in "/", but I am not sure they do that because for example if I have an URL like: http://www.site.com/test then Internet Explorer doesn't add a "/" after it if /test location is handled by a mod_perl handler, but it adds a "/" if /test is a common directory. IE cannot know if /test is a directory or just a virtual path, so "/" might be returned by Apache. Anyway, I am not sure, so I have created a little client with LWP that gets http://www.site.com/test (without a trailing /) and the page is displayed correctly. Teddy
