Re: [users@httpd] mod_rewrite with [last] not behaving as expected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nick Burch wrote:
On Thu, 20 Jul 2006, Neil A. Hillard wrote:
[...]
This is with an internal redirect though, not an external one. No redirect is sent to the client, it's all handled within apache.

In the rewrite logs, you do get:
 applying pattern
 applying pattern
  old path -> new path
 [INTERNAL REDIRECT]
 applying pattern
 applying pattern
 applying pattern
 applying pattern
  new path -> catchall

I would suggest that you'd be better off with rewriting in a Location
block

This is unsupported. Location is per-dir context, too, while the per-dir prefix isn't striped. You're matching against the full physical path. Use it in per-server context instead.

I'm not suggesting that my current rewriting scheme is optimal, just that things aren't behaving as expected

This is how things are working in per-dir context. It stops the rewriting immediately, but there is a request re-processing and if the request reaches your RewriteRules again, they're being processed again.

--
Robert

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux