Jean-Michel Hiver wrote:
>>>PROBLEM HERE >>>A head request should * NOT * return the body of the document >>> >>You should check $r->header_only in your handler. >> >>http://thingy.kcilink.com/modperlguide/correct_headers/3_1_HEAD.html >> > > My only concern is that I thought that Apache::Registry was designed > to act as a CGI emulator, allowing not so badly written CGIs to have > mod_perl benefits without having to change them. > > If I have to use the $r object (and therefore the Apache module), then > it means that the scripts won't be able to run as standalone CGIs... > > Am I right? You can subclass Apache::RegistryNG to do what you want and send the patch for others to re-use. The idea is interesting but while the implementation is possible it won't give any speed benefit. The positive effect that can be achieved is returning the caller exactly what it has asked for. So what you do is you run the registry script as usual but instead of returning the output, you return just the headers. I don't think you can figure out what the headers are going to be without running the whole script (without modifying the script). When I think more about it may be if PerlSendHeader is On, we can adjust the code that parses the script's output in search for headers, to return when it finds the 'Content-type' header. _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
