https://bz.apache.org/bugzilla/show_bug.cgi?id=64447
--- Comment #2 from Oded Arbel <o...@geek.co.il> --- 1. As mod_rewrite internally calculates the directory of the .htaccess and uses it, I think that it would be great to expose that to the configuration language. This would allow us to stop using weird tricks like documented here - https://stackoverflow.com/questions/21062290 - and instead just directly ask the questions we want answered. 2. CONTEXT_DOCUMENT_ROOT is different than document root only in very specific conditions and require server-level configuration - completely out of scope from people writing .htaccess files. RewriteBase assumes that the application writer knows the full path from the document root to the application, which is often not the case when a less technical user downloads an open source application - see the above StackOverflow link for some context. I'm not familiar with any way to resolve relative paths without access to server configuration or pre-knowledge of the path structure of the website - both kind of negate the need for relative paths. 3. Because the current relative path resolution behavior in mod_rewrite is completely unexpected and unreliable in the scope of .htaccess, and also can never expected to work in common configurations (such as under Debian and Fedora/RedHat where httpd is run with cwd set to /), I don't believe there is existing setups that rely on the current behavior. That being said, if the behavior suggested in this report can be triggered by a RewriteOption, that would be good enough. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
