 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | IIS redirect to Apache | IIS redirect to Apache 2007-08-15 - By Martin Gainty
Back
Hi Tony-
Browser clients by and large are prohibited from doing anything on the
clients box except write cookies
the exception for client writes is of course is Applets and Flex objects
..assuming you have neither I would concentrate on using your IIS server as
the reverse proxy as Rainier mentioned both to get LB and Security
provisioning
http://en.wikipedia.org/wiki/Reverse_proxy
Thankfully someone at MIT actually wrote a reverse proxy
http://www.saltypickle.com/Home/16 for IIS
Be cognisant that any ReverseProxy will get ALL traffic and unless you have
configed for max performance you could be placing excessive load on the IIS
box..if you have 1000 connections / day not much load (unless you are doing
alot of file/upload/download activity) is being placed
but 100,000 connections /day requires performance planning
That said
Tomcat was never designed to handle static pages (plain html) and thus the
reason for Apache HTTPD server to handle those pages
The usual scenario is to transmit all requests to Apache HTTPD and then thru
mod_rewrite or VirtualHost send the jsp and servlet to Tomcat
Here are some sample configurations
http://httpd.apache.org/docs/1.3/vhosts/examples.html
Forward vs Redirect
I would use forward instead of redirect as it causes the request to be
bounced back to the client and then up again to the new server
(Then again Im sure Rainier has a reason for making that recommendation)
I hope this works for you ..it sounds quite challenging!
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
-- -- Original Message -- --
From: "Tony Fountain" <tfountain@(protected)>
To: "Tomcat Users List" <users@(protected)>
Sent: Wednesday, August 15, 2007 4:47 PM
Subject: RE: IIS redirect to Apache
Martin,
To clarify our setup, our site receives the initial HTTP request and the
application server in question is IIS and the site is written in
ASP.NET. Some of the pages that will be served will include a frame
that hosts pages from this product hosted by Tomcat on another server.
The current configuration is such that the product invokes some
javascript on the client and the javascript is generating errors
preventing the pages from working properly. The vendor states that this
is due to security issues with the javascript executing across domains
and the way to fix this is to implement a proxy from IIS that redirects
the request (I'm assuming server side but I'm not sure) to the Tomcat
webapp. I'm looking to see if anyone else has any experience they could
lend in creating a proxy from IIS that redirects a request to a Java
webapp hosted by Tomcat on another physical server.
My understanding is I will then be able to reference the URL and make it
look like it's part of the domain running in IIS instead of formatting
another URL in the form of
http://<servername>:<port>/<webapp>/<repository>.
Thanks,
Tony Fountain
Benefit Concepts, Inc.
(419) 244-9936 x9010 (office)
(419) 249-7221 (fax)
-- --Original Message-- --
From: Martin Gainty [mailto:mgainty@(protected)]
Sent: Wednesday, August 15, 2007 4:10 PM
To: Tony Fountain
Subject: Re: IIS redirect to Apache
Kinda O/T here...Which system is front-ending..e.g. which box will be
first to get the HTTP requests?
M--
This email message and any files transmitted with it contain
confidential information intended only for the person(s) to whom this
email message is addressed. If you have received this email message in
error, please notify the sender immediately by telephone or email and
destroy the original message without making a copy. Thank you.
-- -- Original Message -- --
From: "Tony Fountain" <tfountain@(protected)>
To: "Tomcat Users List" <users@(protected)>
Sent: Wednesday, August 15, 2007 1:39 PM
Subject: IIS redirect to Apache
Hi,
Scenario: we purchased a product written in Java to integrate into our
reporting tool. Our setup is such that our web application is written
in .NET and hosted on a web farm using IIS (5 or 6 depending on the
environment). The product we purchased runs under Apache Tomcat/5.5.23
using 1.5.0_12-b04. The product is integrated into our web portal using
frames and sending URL requests to Apache. We are running into issues
with javascript code from the product generating errors for what I
suspect may be related to crossing domains (our web site and the Apache
server). I figure I can resolve this by generating a proxy on the IIS
server to handle the request to the Apache server.
My question is does anyone have any pointers on how to setup this type
of proxy?
Thanks,
Tony
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
This Email has been scanned for all viruses by PAETEC Email Scanning
Services, utilizing MessageLabs proprietary SkyScan infrastructure. For
more information on a proactive anti-virus service working around the
clock, around the globe, visit http://www.paetec.com.
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
|
