Hi all,
 
    I've been testing our Pound proxy for the past week and I'm having some
problems with the trailing slash.  If I connect directly to our backend Tomcat
server using http://my.server.com/fxclink, the
server responds with 302 Moved Temporarily and corrects the url so the browser
connects to /fxclink/.  All the java pages are fine, we're happy.
 
    Pound is listening on port 443 and 80 (for testing).  When I connect
through pound to http://my.server.com/fxclink (missing
trailing slash) the redirect comes through fine, and I'm connected to
/fxclink/.  However when I use https://my.server.com/fxclink, the
page cannot be displayed.
 
    I've captured packets and can easily see the cleartext response code and
corrected location when the exchange is on port 80 through Pound.  The packets
don't have much meaning to me when I capture the encrypted sessions.  
 
    Is this a configuration issue, or am I going about this wrong?  Here's my
(simple) config.  I've tried this with RewriteRedirect set to 1 and 0.  Do I
need to do something else to get RewriteRedirect to work with HTTPS? 
 
User nobody
Group nobody
RootJail /usr/share/pound
LogLevel 2
ListenHTTP 10.10.4.53,80
ListenHTTPS 10.10.4.53,443 /usr/share/ssl/certs/fxclink.pem
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
 
RewriteRedirect 1
 
UrlGroup ".*"
BackEnd 10.10.5.68,80,1
EndGroup
 
Again, thanks so much for the assistance, and putting together such a great
software package.
 
 
Regards,
Tom

On Thursday 03 February 2005 16:03, Thomas Snider wrote:[...]

You'll have to give more information. What do you mean "the page cannot be 
displayed"? What do you see in the browser? What URL is displayed in the 
browser address field?

For easier debugging you could try using something like wget or curl and see 
exactly how the redirect looks on return.
[...]

I suggest you try capturing packets between Pound and Tomcat - that may give 
us a good indication of what is going on.
[...]

This looks fine.[...]