https://bz.apache.org/bugzilla/show_bug.cgi?id=70024
Philippe Cloutier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #4 from Philippe Cloutier <[email protected]> --- (In reply to Joe Orton from comment #2) > This kind of report could be a mailing list discussion on docs@httpd, I > think we should reserve Bugzilla for actual bugs. Despite its name and terminology, Bugzilla is not just designed for bugs. This reports one, however. (In reply to Rich Bowen from comment #3) > On further review, the documentation is correct here. It's not an > inconsistency, rather, it's describing the fact that mod_rewrite behaves > differently in different contexts. Describing several behaviors is not an inconsistency. But the first sentence quoted in the Description is nevertheless incoherent; it assumes a context, whereas, “What is matched?” explains the behavior in the various contexts. By the way, even if the reader could guess it is only talking about the (basically) first non-per-directory rule, it is also misleading to call Substitution a replacement of the original URL-path in that case, since Substitution is not always a path. > I gave some thought to calling this "The input path" or similar. The > difficulty, as described by the flowchart diagram in the > https://httpd.apache.org/docs/current/rewrite/tech.html document, is that > there is not one "input path". Rather, there is a string that can be updated > multiple times (or once, or not at all) as it passes through multiple > rewriting phases, or multiple rules. There's just whatever state it's in at > any given moment. I worry that calling it "input path" suggests that it's a > single value, rather than one point in a process. "input path" was just a quick suggestion. It has the advantage of not being incorrect, but I agree it can be misleading. I guess calling it “subject-path”, with a link to a definition of that, would avoid that, although the meaning may not be as intuitively clear. > The original URL-path becomes a modified URL path (or, sometimes it doesn't) > as it flows through the process. See > https://httpd.apache.org/docs/current/rewrite/tech.html#InternalRuleset for > the diagram referenced. The only fixed point is "The Request" (ie, the > original URL-path) and after that it's all in flux. Right, that's why it should not be qualified as “original”. > I am inclined to close this as WONTFIX because the doc is correct. Willing > to reconsider if someone has specific rephrasings. In the worst case (if consensus on a name is unachievable), this could simply be fixed with: > The Substitution of a rewrite rule is the string that replaces the path that > was matched by Pattern. > Meanwhile, I'm conintuing to go through the entire /rewrite section of the > doc looking for possible improvements. Thanks again Rich -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
