Thanks Bob, this looks like a great tool. It doesn't look like it is too easy to get running on Windows. Do you have it running on Windows?
Jason On Tue, Dec 9, 2008 at 1:04 PM, Palma, Bob <[EMAIL PROTECTED]> wrote: > ** > > Try using software that was built specifically for reverse proxying.. > http://www.apsis.ch/pound/ is a really good one that we use that handles > the HTTPS (port 443) to HTTP (your port 8080) translation just fine. With > so much of the Mid-Tier stuff being Java-based, it is much easier to use a > reverse proxy program than to make a web server (Apache) handle the reverse > proxy. We use Pound for a couple different Java apps and it works really > good. > > > > > > Bob Palma > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Jason Miller > *Sent:* Tuesday, December 09, 2008 4:00 PM > *To:* [email protected] > *Subject:* Proxy Apache Web Server to Tomcat issues > > > > ** We are working on bring up a new web server. We want to use Tomcat for > the JSP engine and run a full Apache web server as the front end as an app > firewall and for static content. We have tried various combinations of > mod_proxy, mod_rewrite and even tried mod_proxy_html. > > > We want to proxy traffic on :443/arsys *to *:8080/arsys on the same > server. Static pages work fine, our proxy for :443/rkm *to *:8080/rkm > works and even the Mid-Tier configuration works from > :443/arsys/shared/config/config.jsp *to * > :8080/arsys/shared/config/config.jsp. > > We also tried setting up a ProxyFilter section in C:\Program Files\AR > System\Mid-Tier\WEB-INF\web.xml as suggested in "Configuring Apache 2.0.x to > work as a Proxy server using mod_proxy on UNIX" (KM-000000025464) without > any success (after restarting Tomcat). > When we try to access an actual Remedy form, the new 7.1 Loading icon sits > in the middle of the page and nothing ever happens, not an even timeout. We > have set the MT logs to Fine and watching the logs do not show any activity > during this Loading period (no looping). > > The last line of the log if access by :8080 directly or through Apaches > :443 is: > > Dec 9, 2008 12:11:38 PM - FINE (com.remedy.log.SERVLET) : > server:<servername>||app:null||form:Home Page||view:Support > View||file:||appResource:null||size:3 > > > Opening the same URL path from :8080/arsys is 93 lines and :443/arsys is > only 30 lines (let me know if you wish to see the missing content, this > posting is getting long enough without it) > > Has anybody else running a full Apache front end had these kinds of issues? > Any suggestions as to the proper way to configure this type of setup (I am > not terribly Apache literate)? > > *Environment* > ---- firewall (only allowing 443 from the cloud) ---- > Web Server > OS: Window 2003 > JSP Engine: Tomcat 5.5.26 Port 8080 > Web Server: Apache 2.2 Port 443 > Mid Tier 7.1 patch 3 > > ---- DMZ ---- > ARS Server > OS: Window 2003 > DB. MS SQL 2005 > ARS 7.0.01 patch 6 > > Thanks, > Jason > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
