Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
From: bugzilla@apache.org
To: docs@httpd.apache.org
Subject: DO NOT REPLY [Bug 52000] RewriteRule documentation
 unclear/misleading about substitution
Date: Fri, 13 Apr 2012 09:37:21 +0000
Message-ID: <bug-52000-56585-flbFwUvL12@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-52000-56585@https.issues.apache.org/bugzilla/>
References: <bug-52000-56585@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

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

--- Comment #12 from Daniel Gruno <humbedooh@apache.org> 2012-04-13 09:37:21 UTC ---
Whether or not the actual file exists does not, at the point of mod_rewrite's
hooking into the process, matter where matching is concerned, so I think your
first argument is moot. In terms of initially matching against a request, a
file path is still valid even though the file itself does not exist. It is only
when you either start substituting or when the file handler kicks in, that it
matters whether the path translates to an actual file.

As for the rest, I have made the necessary adjustments to the two documents.

-- 
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: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org