Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: DO NOT REPLY [Bug 48691] mod_rewrite lost a ground
In-Reply-To: <bug-48691-7868@https.issues.apache.org/bugzilla/>
References: <bug-48691-7868@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-Id: <20100207154850.7CF14234C052@brutus.apache.org>
Date: Sun,  7 Feb 2010 07:48:50 -0800 (PST)

https://issues.apache.org/bugzilla/show_bug.cgi?id=48691

--- Comment #6 from alex yaroshevich <qfox@ya.ru> 2010-02-07 07:48:48 UTC ---
(In reply to comment #5)
> tl;dr version: relying 50% on VirtualDocumentRoot and 50% on per-directory
> rewrites is hard.

Sorry, but not for customer. It`s not intuitive.
When mod_vhost_alias do their job of host virtualization, mod_rewrite do their
self job to rewrites (or not) urls inside host.

I understand that mod_rewrite can do both, but why we have module that is not
useable at full of power? Can we rewrite mod_vhost_alias to mod_vhost_alias2,
for example, which will get all of vhosting troubles to self without any other
problems?
a2moddis vhost_alias if you don`t want to use mod_vhost_alias to
vitrualization.


Just for understanding why I think that is works wrong.
We have a lot solutions for virtualization our apache. But usually used or
mod_rewrite alone, either mod_vhost_alias+mod_rewrite. mod_rewrite alone is
very hard to use but, as i see, working solution. So look at the second. We can
create hundreds of VirtualHost blocks, and can use VirtualDocumentRoot with
exressions. What you choose? Of course, many people starts trying to use
VirtualDocumentRoot. And its not working solution ;-(, but intuitive. Man
searchs WHY it not works properly, found some solutions based on mod_rewrite,
or tried to write conf-generators. So them spend time, because of no good
solution...
And in that time mod_rewrite working after "Virutalization" on each iteration
adds to start of file-path directory. Actually it doesn`t clean it between
iterations as I see bqz have no documentroot or another ground. When we define
some documentroot with virtualdocumentroot it .


Btw, one more possible solution is to add to documentroot some
variables-parsing mechs like %{HTTP_HOST}, or %0, $0 (if it possible,
RewriteCond can write to common variables storage some variables, and, by
default, it can contains parse of http_host like in VirtualDocumentRoot. So the
solution will be to type DocumentRoot and VirtualDocumentRoot in one
VirtualHost block with equal param, for ex: DocumentRoot /path/%-1/%-2.0/%-2/,
VirtualDocumentRoot /path/%-1/%-2.0/%-2/).

By my opinion soft must be intuitive. And creation of common mechs to send
variables to any directive where them can be accessible is very right,
intuitive and useable.

Sorry for a lot of text.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org