On Mon, Dec 28, 2009 at 10:27 AM, R. M. Pretzlaw wrote:
>
> (Which others?)
> anyhow: all of them shall be fulfilled. The VirtualHost on Port 200, the
> "virtual" directory "/foo" and the forwards for non-existent subdirs of
> "/foo/trunk" to "/foo/trunk/_index.php?u={What-Ever-It-Was}". But in th
Eric Covener wrote:
Within an Alias "http://127.0.0.1:200/foo"; that shall use
"G:/Documents/web/foo".
If you stop here, does the Alias work?
Yes. If I turn the "Option Indexes" it shows all sub-directories. Even
the mentioned .htacces is found in "/foo/trunk".
And in "/foo" there exists
> And in "G:/Documents/web/foo/trunk" this .htacces lines when i call
> http://127.0.0.1:200/foo/trunk :
>
> RewriteRule ^[.]{0}$ _index.php?u= [L,QSA]
> RewriteRule ^([^_]+)$ _index.php?u=$1 [L,QSA]
RewriteEngine on?
RewriteBase?
Later in this thread you talk about testing for non-existen
On Mon, Dec 28, 2009 at 9:31 AM, R. M. Pretzlaw wrote:
> Eric Covener wrote:
>>
>> Can you illustrate the same issue without any rewrite?
>
> I guess you mean this (sorry I have to train my English):
>
> There is a VirtualHost on Port 200 e.g.
> It's Document Root is "D:/develop".
> So every call
Eric Covener wrote:
Can you illustrate the same issue without any rewrite?
I guess you mean this (sorry I have to train my English):
There is a VirtualHost on Port 200 e.g.
It's Document Root is "D:/develop".
So every call of http://127.0.0.1:200 leads to this dir.
Within an Alias "http://127
On Mon, Dec 28, 2009 at 9:05 AM, R. M. Pretzlaw wrote:
> The major problem in my case is, that the Alias and Rewriting doesn't
> contain the directory (as the error.log shows). It looks up the files in the
> wrong root.
Can you illustrate the same issue without any rewrite?
--
Eric Covener
cov
André Warnier wrote:
Maybe the first thing is : why use a .htaccess file, when you evidently
have access to the main server configuration.
Because I want to make an application not only for my apache. This makes
it easier for end-users. But I give the hint, too.
I am also a bit puzzled by y
R. M. Pretzlaw wrote:
Whats so confusing about my configutation?
Maybe the first thing is : why use a .htaccess file, when you evidently
have access to the main server configuration.
.htaccess files are probably to most over-used thing in Apache
configurations, and they are quite inefficient,
Hello. Beside other configurations I got this VirtualHost:
DocumentRoot "D:/develop"
Options Indexes FollowSymLinks Includes ExecCGI
AllowOverride All
Order allow,deny
Allow from all
Alias /foo G:/Documents/w
