It does appear that you have everything set up properly.
I'm unable to duplicate the behavior you're seeing, but the environment
I have to test it is Solaris, Apache 1.3.19, Tomcat 3.2.1.
I wonder if it's a bug just with directory listing? Can you get to
servlets or JSP pages via the rewrite rule?
What happens when you do the rewritten url with a trailing slash (e.g.
http://localhost/rewrite/examples/)? There's been some discussion in
the mailing list about handling of trailing slashes, and I seem to
recall there's some issues with that.
Apologies that I couldn't be more help...
dwh
amduser amduser wrote:
>[...]
>
>The rewrite log says
>
>][rid#8650b0/initial] (3) applying pattern '^/rewrite/examples(.*)' to
>uri '/rewrite/examples'
>127.0.0.1 - - [21/Aug/2001:00:05:25 -0400]
>[foo.lan/sid#7a60f0][rid#8650b0/initial] (2) rewrite /rewrite/examples
>-> /webapps/examples
>127.0.0.1 - - [21/Aug/2001:00:05:25 -0400]
>[foo.lan/sid#7a60f0][rid#8650b0/initial] (2) forcing
>'/webapps/examples' to get passed through to next API URI-to-filename
>handler
>
>* Response to http://localhost/webapps/examples:
>
> ... correct directory listing ...
>
>* Response to http://localhost/rewrite/examples:
>
> Not Found (404)
> Original request: /rewrite/examples
> Not found request: /rewrite/examples
>
>[...etc...]
>
