> The text seems rather to imply that the description/example is supposed to be > as it is, > but then the behaviour described is somewhat "counter-intuitive", i.e., I > don't see how > I could have deduced it from the descriptions of RewriteOptions and <If>. > The description of RewriteOptions Inherit at > https://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewriteoptions > does explicitly mention the case of per-directory context, and then > only talks about merging rules from the _parent_ context, not from > _sibling_ contexts.
I think the root cause of all of this is that rewrite barely made sense in non-htacess directory contexts, and then was tolerated in Location, and then further tolerated in <If>. So code/doc that were primarily about htaccess now apply differently. Further, if it was intuitive it would probably omitted from the docs. Maybe there should be a prominent "warn" type note about using Rewrite in <if>, outside of RewriteOptions. It's often necessary because there are no lower level primitives that you can use inside <If> to take the same actions as mod_rewrite. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
