httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Malo ...@perlig.de>
Subject [PATCH] make unique id generation configurable
Date Tue, 03 Dec 2002 14:18:29 GMT
don't know whether it makes sense in general, but it just makes sense for 
me ;-) Instead of generating a unique id for *every* request, it seems 
better to give the user the possibility of restricting it to some files 
(cgi-scripts etc.)

The attached patch works for me, but I'm not sure, that I considered all 
implications (subrequests? etc.) However, it does the following:

- introduce the directive UniqueID On|Off, that is allowed everywere   
  (.htaccess with AllowOverride Options)
- it hooks the id generation additionally into header_parser, so directory  
  configuration gets a chance to be applied.
- for backwards compatibility I kept the post_read_request hook, that 
  generates the unique ID, if the server config says "On" (or unset).
  Of course, once generated you cannot disable the ID generation; the 
  apache throws a warning, if someone is trying that.
  That means, you have to set globally UniqueID Off, in order to get any 
  effect due to directory configuration.
  
If there's something bogus or could be done better, please tell me...  

TIA, nd
-- 
my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~});
my $japh = q[sub japh { }]; print join       #########################
 [ $japh =~ /{(.)}/] -> [0] => map $_ -> ()  #            André Malo #
=> @japh;                                    # http://www.perlig.de/ #

Mime
View raw message