You should know where they're coming from the same way you do in mod_rewrite. Besides that, referers can be spoofed, and I some clients don't even give you a referer...
Issac ----- Original Message ----- From: "Gary C. New" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 12:19 PM Subject: Shared SSL Custom Log Parsing > I've got shared ssl setup with mod_rewrite and I am trying to figure out > the best way to direct logging for each of the vhosts using the shared > ssl connection and thought mod_perl might be good for this. > > My thinking is to setup a <PERL> section in the httpd.conf file that > watches the referrer environment variables as they come in for the > shared ssl connection and then rewrite them to the appropriate custom > vhost access/error logs. > > Referrer Variable: > > https://secure.provider.tld/secure/domain.tld/ > > Rewrite Logs: > > CustomLog /home/domain.tld/logs/access.log > ErrorLog /home/domain.tld/logs/error.log > > or > > I noticed on the perl.apache.org site an example called "Logging to > syslog" that could be used similarly but for the custom access/error > logs. It pipes the general incoming logs to a program that then parses > and rewrites the logs appropriately. > > I guess my main question with either example is what is the best way to > write the parsed logs to these custom log files? Is there an existing > module for this purpose? > > Is there a better way to parse and rewrite logs to custom files on-the-fly? > > Respectfully, > > > Gary > > > > -- > Report problems: http://perl.apache.org/bugs/ > Mail list info: http://perl.apache.org/maillist/modperl.html > List etiquette: http://perl.apache.org/maillist/email-etiquette.html > -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
