DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=26052>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=26052 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] ------- Additional Comments From [EMAIL PROTECTED] 2006-02-03 20:55 ------- I bumped into this bug again, now in apache 1.3.33. I have been trying to work around it in an older version, using mod_rewrite, but it just won't modify DOCUMENT_ROOT. Question : if VirtualDocumentRoot is in fact [actual end result] doing the same thing as DocumentRoot, but for a mapping scheme instead of a static path. So why doesn't mod_vhost_alias with this directive give us the correct answer? Because as someone said earlier, without this, the whole module is pretty much useful just for static sites with no, or minimal scripting. And a lot of drag from cgi developers in my vhosts. Had mod_rewrite had write access to this variable, I could've worked around the bug directly a looong time ago, but it doesn't. So, sadly, I just have to scrap the "motivation behind mod_vhost_alias" as in the docs, and go back to my pile of virtualhosts, all statically typed :( Another VRITUAL_DOCUMENT_ROOT directive ? I really suggest setting DOCUMENT_ROOT to the proper value. I did build a mod_rewrite hack once, creating some sort of mass vhosts and used it to create another ENV variable to specify the proper document root as generated by mod_rewrite. Since such a "dirty hack" can be done in mod_rewrite, I really don't see the point in porting the "dirty hack" into the server itself. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
