[Mod_log_sql] LogSQLMassVirtualHosting and mod_vhost_alias

webmaster at gleitgeb.at webmaster at gleitgeb.at
Mon Jan 23 04:36:48 EST 2006

> The current version of my patch will work as you specified under both
> these situations, any two character (or less) entries will be treated
> as part of the xLD.  It doesn't do any checking to see if the xLDs are
> valid, but I don't see any problem with that as any FQDNs being hosted
> would presumably be registered somewhere.  We don't need to be quite
> as strict with our checks as a SPAM filtration or e-mail address
> verification program, we just need to be able to distinguish xLDs from
> the rest of the FQDN.

That's also my opinion.
It's not possible that requests with non existing xLDs getting to a
webserver because they cannot existing in a Nameserver.

>I think you'd run into the same sorts of problems using an
>interpolation routine as we've been discussing here, or at least I
>haven't been able to think of a way to get a mod_vhost_alias
>interpolation that doesn't exhibit simmilar problems.  For instance,
>we're currently using the following:

>VirtualDocumentRoot /var/vhosts/%-1/%-2.1/%-2.2/%-2.3/%-2/htdocs/%-3+/

>So www.example.somesite.com would have its DocumentRoot in
>/var/vhosts/com/s/o/m/somesite/htdocs/www.example/ .  As I discovered
>during my recent testing of .co.uk sites, www.somesite.co.uk ends up
>having its DocumentRoot in
>/var/vhosts/uk/c/o/_/co/htdocs/www.somesite/ .  My point here is that
>there's no real way to tell the interpolation routine how to skip back
>however far it needs to for the xLD.

I have the same problem ...

I use a mod_rewrite routine instead.
But this is quite much memory consuming but I cannot find a better solution
for that.

More information about the Mod_log_sql mailing list