First, thanks for your assistance with this, I appreciate the time and effort. It's quite possible I'm using it wrong. In IIS, I setup a site with root drive on C:\inetpub\r18test2.kcc.edu and I created two virtual directories, 1 for the isapi dll called jakarta and another for the WebAdvisor2 folder in tomcat called WebAdvisor2. If someone goes to http://r18test2.kcc.edu, you get the default doc in the C:\inetpub\r18test2.kcc.edu folder, which is where I put the meta redirect. However, if you type http://r18test2.kcc.edu/WebAdvisor2/WebAdvisor2, you get redirected, I'm assuming through the isapi dll, to http://10.10.11.90:8080/WebAdvisor2/WebAdvisor2. So it appeared to me that the isapi was working. Does that make any sense?
>>> André Warnier <a...@ice-sa.com> 3/9/2010 12:50 PM >>> André Warnier wrote: > Joshua Gregoire wrote: >> r18test2.kcc.edu brings me to the root drectory of the site in IIS. I >> have a redirect set on the default page in IIS to go to >> http://r18test2.kcc.edu/WebAdvisor2/WebAdvisor2 > The url in the >> browser then changes to http://10.10.11.90:8080/WebAdvisor2/WebAdvisor2 > > > The first question is then : if you are anyway redirecting everything to > Tomcat, why do you need to have IIS in front ? > Why not just set Tomcat to answer port 80, and get rid of IIS ? > > The second item is : > In the URL bar, the browser displays what its own idea is, about where > it got the current page from. > The same, just in other words : nothing which the server sends to the > browser, is displayed in the browser's URL box. > The same again, in yet other words : try to create a page on the server > which writes something into the browser's URL bar. Or rather, don't try, > because you would be losing your time : you can't. The server does not > have access to the browser's URL bar. > > So, the fact that the browser's URL bar displays "10.10.11.90" is due to > the fact that the browser obtains the current page from the host named > "10.10.11.90". And the one thing that can tell it to get the page from > there, is the redirect response from IIS. Concentrate on that one. > How /exactly/ do you do this redirect from the IIS homepage to the > Tomcat server ? > > Something else strikes me (and I wonder why it did not before) : You say that you have IIS + the isapi_redirector, to connect IIS to Tomcat. But if you really "redirect" calls to the homepage of IIS, to Tomcat's port 8080, you are not using the isapi redirector at all. You are just "bouncing off" once from the IIS homepage, and all the rest happens directly between the browser and Tomcat, on port 8080. Something tells me that you are not quite using this kind of setup as it is meant to be used. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
