Usually (and slightly naughtily) I add this to the access handler within mod_perl {it does the user/ip identification and then performs the appropriate filters}
If you are doing complex access layers (e.g. checking permissions in a db) you may not be able to do this with Location/LocationMatch
On 19/07/2016 07:14, Nick Kew wrote:
On Tue, 2016-07-19 at 10:45 +0530, Amlaan Kar wrote:I have created a handler in ApacheSounds like your module's processing should be hooked up earlier in the cycle. It can then set the handler either to PHP or to its own page according to the outcome of whatever parsing it does. But given that the server parses the URL, you can probably dispense with that altogether, and use configuration to deal with whatever your parser does. If <Location> or <LocationMatch> is not sufficient, then an <If> clause. Or even the archaic tool of yesteryear, mod_rewrite.
--The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx