It depends of how you map/forward from apache to resin.
What is your apache configuration?
If it works when you access resin directly, what is done when you access
throught port 8080, then it's not a resin problem.
smallufo wrote:
Yes , I use Apache as a front end.
If any configuration goes wrong , servlets' requests will not be processed
by resin, either.
But http://foo.bar.com/servlet/other.servlet just works fine. (No port
assign)
It means resin (2.1.7) seems doesn't intercept filter's requests.
I've also reported this issue to resin's maillist.
2007/10/2, David Bernard <[EMAIL PROTECTED]>:
If I understand right you use Apache as a front end ?
If it work when you access to resin via a direct call (
http://foo.bar.com:8080/app) then I don't think it a problem with resin
but with your apache front-end configuration.
What do you "map" from apache to resin (1)/app, (2)/app* or (3)/app/* ?
In my experience you need to map (1 and 3) or 2. You don't need to map 1
and 3 only if you have a rewrite rule /app => /app/.
Yes , I tried but in vain.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
