This ended up being my error. I figured out I could
change the log level of the ISAPI redirector and I put
it to inform level. I saw that for the non-proxy site
request it saw /servlet/class but for the proxied
request it saw //servlet/class so it didn't match
the worker mapping.
I checked my proxy config and that's where I was
picking up the extra "/". I swear this was the
configuration I had used before. Maybe the iPlanet
server was being more forgiving of my sloppy URL
rewriting. It's funny that IIS only saw it as
/servlet too--maybe it's forgiving too but the ISAPI
redirector isn't. Oh well, just a few hours lost. I
should have checked the detailed logging yesterday.
Live and learn.
--- Randy Layman [EMAIL PROTECTED] wrote:
Is it possible that either the filter of virtual
directory aren't
set up for the virtual host being used by the proxy
but are for the virtual
host serving up the internal requests? (From my own
experience, IIS is very
picky and sometime very odd in its choice of which
virtual host to use for a
given request).
Randy
-Original Message-
From: Ray Rush [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 12, 2001 9:49 AM
To: [EMAIL PROTECTED]
Subject: IIS - ISAPI redirector oddities
I've spent quite some time looking around on the
FAQ,
documentation and other resources trying to find
an
answer to this but have found nothing. Please
take a
look.
I have a Win2k Pro machine with IIS 5.0. Tomcat
3.2.1
is installed and working just fine. The ISAPI
redirector works great with this setup. However,
this
machine is hidden from the outside. If I use
mod_proxy w/Apache 1.3.12 (Solaris 7) to pass
requests
to this machine, the filter does not catch the
/servlet
in the URL so Tomcat doesn't get the request.
The
URL is
'http://hostname/servlet/com.esri.esrimap.Esrimap?ServiceName=swdms'.
This proxying scenario has worked for me
previously on
an NT4 machine using the iPlanet FastTrack server.
But on Win2k with IIS and the ISAPI redirector it
just
fails.
I've very confused on why the '/servlet/*=ajp12'
line
in uriworkermap.properties works when done purely
on
the native machine but not when proxied by Apache
it
bombs.
When it is successfull, my IIS web log has the
line
'POST /jakarta/isapi_redirect.dll 200',
but when it fails I see
'POST /servlet/com.esri.esrimap.Esrimap 405'.
The 405 error means post/get is being used on a
page
that does not allow post/get. To me, the filter
just
isn't handling the redirect properly.
I hope this is something that is obvious to those
with
better knowledge of how the redirector works. Any
hints/tips/suggestions will be greatly
appreciated.
And yes, I am confined to the NT world for this
particular servlet application.
Ray Rush
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
