Hi,

one addition:
in a configuration like

client   
->  apache.somewhere.com:80       
->  tomcat.somewhere.else.com:8080

you could play around the the apache directive 
ProxyPreserveHost On

This keeps the hostname "apache.somewhere.com:80"  in the request header and 
should solve your problem.

Using this another problem arises:

client 
->  https://apache.somewhere.com:443 
->  http://tomcat.somewhere.else.com:80 

is still a problem as the request type https is not preserved.

Best Regards,
        Ilja Pavkovic


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Janak Mulani
Sent: Thursday, June 15, 2006 10:50 AM
To: Hofmann, Torsten
Cc: [email protected]
Subject: RE: [ULC-developer] ULC over Apache


Hi Torsten,

There is already an issue: http://www.canoo.com/jira/browse/UBA-5744.

Some colleagues have had expreience with server side proxies and they offer
the following tips:

There are different way one can use tomcat together with apache:

1. by using ajp13-connector (or ajp12)
or
2. by using http and apache as a server side proxy.

If apache is configured as server side proxy it itself performs
http-requests at the tomcat-http-server => the Servlet only sees a request -
URI that points into the tomcat server and not the apache server.

Example:

client   ->  apache.somewhere.com:80       ->
tomcat.somewhere.else.com:8080

=>  the ULC Application running on tomcat.somewhere.else.com  only can see
requests to tomcat.somewhere.else.com:8080 and therefore probably is
generating URLs that use this as a basis.

The .jsp's that generate the applet-tag, ... should show the same problem.

One solution could be to use ajp13, because it transports the original
request headers and URI to tomcat.

Another one, to somehow configure the ULC-Application to know about
apache.somewhere.com.

If you make use of absolute URLs in your ULC application (e.g. the
application-url in the JSP, or an URL to
be opened via ClientContext.showDocument()) and if you use a server side
proxy, these absolute URLs finally point
to the application server and not to the server side proxy (i.e. Apache in
your case).

1. pass the context URL to your application and use this to calculate the
absolute URLs => this is a deployment dependant element that has to be
adapted for each deployment

2. use relative URLs in your application and calculate the absolute URL on
the client => only works with Applets
For this you will have to implement a custom Applet launcher that could
handle relative URLs for both, application-urls and
ClientContext.showDocument() URLs. As URL root you need to use the Applets
document base (Applet.getDocumentBase()).

I hope this helps.

Thanks and regards,

Janak


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Hofmann, Torsten
Sent: Tuesday, June 13, 2006 12:07 PM
To: [email protected]
Subject: [ULC-developer] ULC over Apache


Hello

Is it possible to run a ULC Application in this way


ULC-Server(Tomcat) --> Apache --> Internet

When i try this i get an error for example in the method
ClientContext.showDocument, because the application tried to reach the file
at the tomcat server.

Could someone give me a hint.

Regards

Torsten Hofmann
Dipl. - Informatiker (FH)
IT Consultant Business Integration

Würth Phoenix GmbH
Drillberg 6
D-97980 Bad Mergentheim

(Phone: +49 7931 91 6284
7 Fax: +49 7931 91 7284
+E-Mail: [EMAIL PROTECTED]
     Website: www.wuerth-phoenix.de

_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer

Attachment: mod_proxy - Apache HTTP Server.URL
Description: mod_proxy - Apache HTTP Server.URL

Reply via email to