Hi everyone,

 

We currently have an interesting problem which I was hoping someone else
here may have encountered and resolved.

 

Our current setup is Pound as a front end receiving HTTPS requests and
passing them to a Tomcat backend via HTTP. Tomcat then automatically
generates the Web Service information, but it generates it with HTTP
URLS not HTTPS urls which is what we want. 

 

For example, here's a sample web service information page.

 

Web Services

Port Name   Status      Information

                        Address:
http://alpha.navman.com:443/ecomif-jaxrpc/ecomif

WSDL:
http://alpha.navman.com:443/ecomif-jaxrpc/ecomif?WSDL

EcomIF      ACTIVE      Port QName:
{https://prod.navman.com/wsdl/EcomIF}EcomIfIFPort

Remote interface:       com.navman.landnav.ecomif.EcomIfIF

Implementation class:   com.navman.landnav.ecomif.EcomIFImpl

Model:
http://alphanavman.com:443/ecomif-jaxrpc/ecomif?model

 

Ideally, all of the alpha.navman.com URLs should be HTTPS, not HTTP as
Pound is only listening for HTTPS requests, but I guess Tomcat doesn't
know this.

 

Does anyone have any ideas on how to convince Tomcat to generate the web
services information correctly when using Pound as an HTTPS front end?
Or any other possible solutions / work arounds?

 

Regards,

Sarah

It isn't quite clear from your question whether these URL's are internal to
the returned responses in the form of absolute URL's or whether these are
redirects.

Depending on your situation, the answer may be that pound is not able to
resolve the host names in question so that it can rewrite URL's.  This would
be the case with redirects.

IF the URL's are embedded in response bodies, then you probably need to
tweak your tomcat application to tell it that these other services should be
behind an HTTPS URL rather than an HTTP.

IF you aren't sure of your situation, you should do some packet tracing and
present a detailed synopsis of the situation.


On 9/19/06 2:47 PM, "Sarah Brennan" <sarah.brennan(at)navman.com> wrote:
[...]