I was reading bug reports this morning, and wondered if someone could take a look at the patch offered here:

https://issues.apache.org/bugzilla/show_bug.cgi?id=26052#c19

It adds a SetVirtualDocumentRoot configuration directive to mod_vhost_alias, making numerous third-party applications behave sanely when run under mod_vhost_alias.

I've read the various justifications why we don't do this, and quite frankly I don't understand them. Is there a legitimate reason that setting DOCUMENT_ROOT on a per-dynamic-vhost basis is any different/ worse than setting it on a per-regular-vhost basis? I don't understand the distinction, other than "we've never done it that way."

Thanks.

--
Rich Bowen
rbo...@rcbowen.com

Reply via email to