Henrik,
Thank you for the reply, but I'm afraid I don't quite understand your
answer. I thought that configuring external DNS to point
'backend.foo.com'at the squid box would be sufficient to deal with the link
problem. In fact, when I make squid listen to http on 8015, it handles the
links fine.
It's the squid-to-client redirect from http 8015 to https 443 that I seem
to be having trouble with.
I hope you can clarify your point, and perhaps point out a solution other
than modify the application. While I want SSL for a new group of internet
users, I am restricted from changing the application (Oracle 11i self
service) in any way due to impact on internal inside users.
Thanks and have a great weekend,
Mike
Henrik Nordstrom
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.org> cc: [EMAIL PROTECTED]
Subject: Re: [squid-users] please help
- looping 301/302 redirect in an ssl reverse
01/23/2004 04:25 proxy
PM
On Fri, 23 Jan 2004 [EMAIL PROTECTED] wrote:
> The login page to the backend server got proxyed correctly, but after
logon
> the return traffic to the client contained frames with links to
> 'http://backend.foo.com:8015'.
Then you need to fix your application to use relative links. Absolue paths
is also OK.
Regards
Henrik
