Details on IIS/Tomcat Question

2002-06-07 Thread Harlan Messinger

Hi, my colleague Chris got here before I had signed onto the group, but
let me fill in some details about our attempt to get IIS to work with
Tomcat. We want to do this because we have JSP files sharing directories
with static HTML files, *and* we also have Cold Fusion files.

This is Tomcat 4.0.3 on Windows 2000.

I created a web site in IIS, and configured it to intercept all requests
on port 8765. I set its root directory to the webapps directory in the
Tomcat installation. I added a virtual directory called jakarta, with
root directory in the Tomcat bin directory.

The DLL that was present in the FTP area was isapi_redirector.dll. I
registered it as an ISAPI filter, and got a green arrow when I restarted
the site.

In SERVER.XML, after the Server tag, I added the tag

Listener className=org.apache.ajp.tomcat4.config.IISConfig /

After the Host tag with name localhost, I added the tag

Listener className=org.apache.ajp.tomcat4.config.IISConfig 
noRoot=false forwardAll=false append=true / 

I added the noRoot and forwardAll attributes late during my attempts to
get this to work. They had no effect on the results as far as the JSP
pages are concerned.

I uncommented the Context tag for the root path.

Here's my iis_redirect.reg, which I have loaded into the Registry:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi
Redirector\1.0]
extension_uri=/jakarta/isapi_redirect.dll
log_file=..\\logs\\iis_redirect.log
log_level=emerg
worker_file=..\\conf\\jk\\workers.properties
worker_mount_file=..\\conf\\auto\\uriworkermap.properties

The uniworkermap.properties file is exactly as Tomcat created it.

In the jk directory I added file worker.properties, including the
following entries that differ from the version in the ajp.html document:

worker.tomcat_home=C:\tomcat\jakarta-tomcat-4.0.3
worker.java_home=C:\jdk1.3.0_02

I created a JAVA_HOME environment variable, pointing to C:\jdk1.3.0_02.

I couldn't help noticing that the extension_uri in the Registry entry
has isapi_redirect.dll instead of isapi_redirectOR.dll. I finally
noticed that the instructions say to download the Tomcat 3.3
isapi_redirect.dll! Then why is there a file with a different name in
the Tomcat 4.0.3 area, and what's THAT supposed to be for? Anyway, I
downloaded isapi_redirect.dll, and substituted it for the other file in
the ISAPI Filters config. I get a RED arrow. Why should that be?

Anyway, even before switching the ISAPI filter, a request for

http://myserver:8765/examples/jsp/colors/colors.html

works, but a request for


http://localhost:8765/examples/jsp/colors/colrs.jsp?color1=redcolor2=bl
ueaction=Submit

gives me The specified module could not be found. Using Tomcat's
built-in HTTP service,


http://localhost:8080/examples/jsp/colors/colrs.jsp?color1=redcolor2=bl
ueaction=Submit

does work, so Tomcat itself isn't the problem, it's the redirection. In
fact, the log file, iis_redirect.txt, that's supposed to appear in the
logs directory, never does.

Any thoughts?

Harlan Messinger

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: Details on IIS/Tomcat Question

2002-06-07 Thread Harlan Messinger

OK, thanks. You're right, it still didn't help :), but I got my green
arrow back.

I can't help wondering about the number of people who try to link IIS
and Tomcast 4 together, *all* having to go through this exercise.

 -Original Message-
 From: Wagoner, Mark [mailto:[EMAIL PROTECTED]]
 Sent: Friday, June 07, 2002 8:28 AM
 To: 'Tomcat Users List'
 Subject: RE: Details on IIS/Tomcat Question
 
 
  I couldn't help noticing that the extension_uri in the 
 Registry entry
  has isapi_redirect.dll instead of isapi_redirectOR.dll. I finally
  noticed that the instructions say to download the Tomcat 3.3
  isapi_redirect.dll! Then why is there a file with a 
 different name in
  the Tomcat 4.0.3 area, and what's THAT supposed to be for? Anyway, I
  downloaded isapi_redirect.dll, and substituted it for the 
 other file in
  the ISAPI Filters config. I get a RED arrow. Why should that be?
 
 Your are correct, the registry entry is wrong.  Switch back 
 to the 4.0 DLL
 and change the registry value to isapi_redirector.dll.  This 
 may not fix all
 the problems but at least you should get a green arrow again.
 
 --
 To unsubscribe, e-mail:   
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: 
 mailto:[EMAIL PROTECTED]
 
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: Problems in redirecting requests from IIS to Tomcat 4 (new Information)

2002-06-07 Thread Harlan Messinger

Luca,

Does there have to be a separate Host tag for each host name? I
haven't gotten this far, but since the default Host tag has the name
localhost I'm deducing that it's only good for requests that come in
for the host localhost. To be sure, this seems clunky, since it means
you have to duplicate and maintain the entirety of the tag and its
contents for every host name you want to use, so I'm not sure I'm
interpreting this correctly.

But since you do seem to have it working for localhost, could you tell
me if, from the information I provided here this morning, you can see
what step I might be overlooking?

Harlan

 -Original Message-
 From: Luca Ventura [mailto:[EMAIL PROTECTED]]
 Sent: Friday, June 07, 2002 9:55 AM
 To: Tomcat Users List
 Subject: R: Problems in redirecting requests from IIS to Tomcat 4 (new
 Information)
 
 
 Escuse me all in the forum
 
 I want to point out that in my server.xml of Tomcat I have 
 the following
 entries:
 
 !-- Define the default virtual host --
 Host name=localhost debug=0 appBase=webapps unpackWARs=true
 
 !-- Define the top level container in our container hierarchy --
 Engine name=Standalone defaultHost=localhost debug=0
 
 
 Maybe I have to modify them and set as Host 
 www.mydomain.com (or the IP
 address of my Web Server) instead of localhost?? In fact 
 the Web Server's
 name isn't localhost any more but www.mydomain.com
 
 Thanks a lot in advance!
Luca
 
 -Messaggio originale-
 Da: Wagoner, Mark [mailto:[EMAIL PROTECTED]]
 Inviato: venerdì 7 giugno 2002 14.48
 A: 'Tomcat Users List'
 Oggetto: RE: Problems in redirecting requests from IIS to Tomcat 4
 
 
 If I recall...
 
 Go to the Properties page of the web server and select the Directory
 Security tab.  Click the Edit button for Anonymous Access and 
 Authentication
 Control.  Select Anonymous Access and un-select everything under
 Authenticated Access.
 
 HTH
 
 -Original Message-
 From: Luca Ventura [mailto:[EMAIL PROTECTED]]
 Sent: Friday, June 07, 2002 8:38 AM
 To: tomcat-dev; tomcat-user
 Subject: Problems in redirecting requests from IIS to Tomcat 4
 
 
 Hello everybody!
 
 I have installed Internet Information Services (IIS) as Web 
 Server  and
 Apache Tomcat 4.0 as plug-in of IIS to support JSP-Servlets 
 (to do this I
 installed an ISAPI filter in IIS that redirects
 all my JSP-servlet requests to Tomcat). All works fine when I am on
 localhost but if I use
 another domain for my Web Server (e.g: www.mydomain.com) I have the
 following problem: when I try to connect to a site that must 
 be redirected
 to Tomcat 4 (because it contains JSP pages or servlets), IIS 
 ask me a login
 or a password to access to it. For example: i try to connect 
 to the url
 http://www.mydomain.com/mysite; and mysite is a web 
 application defined
 in webapps folder of tomcat (the document folder is in
 webapps\mysite\web-inf).
 
 What can I do to avoid IIS asks me a password or a login? I 
 want that all
 users that connects to my site  are redirected to Tomcat 
 without asking any
 login and password
 
 I think the problem it isn't in Tomcat's configuration but in IIS's
 configurationbut I can be wrong.
 
 I hope someone can help me...thanks i advance!
 
  Luca
 
 
 --
 To unsubscribe, e-mail:
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
 mailto:[EMAIL PROTECTED]
 
 --
 To unsubscribe, e-mail:
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
 mailto:[EMAIL PROTECTED]
 
 
 --
 To unsubscribe, e-mail:   
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: 
 mailto:[EMAIL PROTECTED]
 
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




IIS/Tomcat redirection solved

2002-06-07 Thread Harlan Messinger

Folks,

Chris Ruegger and I solved the problem we reported earlier. I had
isapi_redirector.dll properly installed as an ISAPI filter for the
*site*, but we discovered that ISAPI filters are also installed at the
*server* level, and one of them was from a JRun installation that I'm no
longer using. I removed that, and now IIS is routing JSP pages onward.

Now, we have a new pair of problems, which I'll report under a new
subject line.

Harlan

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




IIS/Tomcat: scriptlets, POST not working

2002-06-07 Thread Harlan Messinger

In my new IIS/Tomcat configuration, IIS *seems* to be forwarding
requests for JSPs to Tomcat, because it displays them. IIS on its own
doesn't display JSPs, it just asks if you want to open them or save them
to your local drive.

BUT: the scriptlets and expressions aren't being executed, so only the
HTML is being rendered. 

AND: Only GET works. POST doesn't work. POST gives HTTP status code 405,
which Internet Explorer identifies as Resource not allowed, though the
W3C HTTP spec says it's Method not allowed.

Regarding the first problem above: I'm interested to note that the IIS
web log shows HTTP status code 200 for the GET when the request
immediately follows a change I've made to the JSP page, and a 304
(Resouce Not Modified) for subsequent requests. My question is: why
does IIS record an entry at all when it isn't the server that ultimately
serves the page? And now I see that the Tomcat logs don't show any
record of receiving these requests. And no log called isapi_redirect.txt
is being created as it should be. It's as though IIS now feels empowered
to handle JSP requests by itself--but since it doesn't know how to
handle JSP, it ignores it, and just serves the HTML.

Ideas? Thanks.

Harlan Messinger

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: IIS/Tomcat: scriptlets, POST not working

2002-06-07 Thread Harlan Messinger

It DOES seem to be that IIS is handling the JSP pages itself: the same
thing happens even when Tomcat is shut down.

I checked, and there are no other ISAPI filters or app filters handling
JSP files in the web site I set up for Tomcat OR at the server level.

 -Original Message-
 From: Harlan Messinger 
 Sent: Friday, June 07, 2002 1:33 PM
 To: Tomcat Users List (E-mail)
 Subject: IIS/Tomcat: scriptlets, POST not working
 
 
 In my new IIS/Tomcat configuration, IIS *seems* to be forwarding
 requests for JSPs to Tomcat, because it displays them. IIS on its own
 doesn't display JSPs, it just asks if you want to open them 
 or save them
 to your local drive.
 
 BUT: the scriptlets and expressions aren't being executed, so only the
 HTML is being rendered. 
 
 AND: Only GET works. POST doesn't work. POST gives HTTP 
 status code 405,
 which Internet Explorer identifies as Resource not allowed, 
 though the
 W3C HTTP spec says it's Method not allowed.
 
 Regarding the first problem above: I'm interested to note that the IIS
 web log shows HTTP status code 200 for the GET when the request
 immediately follows a change I've made to the JSP page, and a 304
 (Resouce Not Modified) for subsequent requests. My question is: why
 does IIS record an entry at all when it isn't the server that 
 ultimately
 serves the page? And now I see that the Tomcat logs don't show any
 record of receiving these requests. And no log called 
 isapi_redirect.txt
 is being created as it should be. It's as though IIS now 
 feels empowered
 to handle JSP requests by itself--but since it doesn't know how to
 handle JSP, it ignores it, and just serves the HTML.
 
 Ideas? Thanks.
 
 Harlan Messinger
 
 --
 To unsubscribe, e-mail:   
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: 
 mailto:[EMAIL PROTECTED]
 
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]