https://bz.apache.org/bugzilla/show_bug.cgi?id=58892
--- Comment #1 from Rich Bowen <[email protected]> --- I'm finally circling back to this, 10 years later. The plan is a comprehensive reorganization of the rewrite guide. The "advanced" doc will be dissolved — its recipes redistributed to topically appropriate files (remapping, flags, rewritemap, avoid). The file itself will be reduced to a deprecation stub so that external links and bookmarks continue to work. The same treatment applies to access.xml and proxy.xml, whose content is being consolidated into avoid.xml — since every recipe in both files already contains a "don't use mod_rewrite for this" discussion, they belong there. The empty htaccess.xml stub will be populated with substantive content about per-directory rewriting, RewriteBase, and .htaccess-specific gotchas. Beyond the reorganization, the content itself is getting a modernization pass. Recipes that reference obsolete patterns (Netscape 3 browser detection, CGI handler tricks, country-TLD geo-routing) will be removed. New recipes will be added for the things people actually search for in 2026: HTTPS enforcement, trailing slash normalization, www canonicalization, and front-controller routing. The flags reference will get better examples for the newer flags added in the 2.4.x cycle (BCTLS, BNE, BNP, QSL, END). Throughout, the guide will more actively steer readers toward native alternatives — <If>, FallbackResource, Redirect, ProxyPass — rather than treating mod_rewrite as the default answer. This will land as a series of commits: mechanical reorganization first (recipe redistribution, stub creation, cross-reference updates), then content modernization (new recipes, obsolete recipe removal, flags improvements, security guidance). -- 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]
