Neal,
> For someone unfamiliar with these things [do] you think
> it would be easier to [move] Apache in front of it, or
> is it easier to write [a Filter?]
I would be comfortable with either, but I've already apache as the front end
and experience with mod_rewrite, so I'd go for the 30 second solution before
writing a new Filter. What are you more confident in your ability to do?
Develop a new Filter in Java, or install apache as a front end? The only
person who can answer that is you.
> [would] these mappings filters and rewrites [occur]
> prior to initial output and result in a completely
> normal, well-formed server header for a requested
> document? I mean, http status code would be
> Would there be any clue to a search engine that any
> of these things aren't what they appear to be?
The user-agent wouldn't have a clue. The only "tricky" thing would be that
if you don't have a Filter to rewrite outbound URLs, you want to write your
tags as <a href="/mypath/mdlx/page.html" so that they are returned that way
to the user-agent. Then you just map them to "/mypath/page.mdlx" on the way
into tomcat. But as far as the user-agent is concerned, it gave you
"page.html", and it has no idea that you gave it back the content from
"page.mdlx."
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
