Thanks for your help. I actually wasn't attempting to use url redirection at the same time as the tcprelay, but rather as a possible alternative. In any case, what you said below makes sense.
To troublehsoot this issue, I started Delegate 8.1.0 Win32 with this command-line (sslway is working fine):
< DIV>delegated -v-P500 FCL=sslway ADMIN="test@" PERMIT="*:*:*"
It seems that when I connect to any redirected URL that doesn't have a "/" after the hostname, it will try to connect to it using http instead of https and subsequently fail.
When I type in https://127.0.0.1:500/-_-http://www.yahoo.com Internet Explorer automatically tries to connect as http://127.0.0.1:500/-_-http://www.yahoo.com/ (it replaces the "https" with "http" and adds a "/" at the end). This fails.
So instead I type in https://127.0.0.1:500/-_-http://www.yahoo.com/ (with a trailing "/") directly and it works fine first try.
Incidentally, the BASEURL switch does not seem to affect this behavior.
If I start delegate without the FCL=sslway, everything works fine no matter how the URL is typed (and it will automatically add the "/").
From: Yutaka Sato [mailto:firstname.lastname@example.org]
Sent: Sat 11/30/2002 7:56 AM
Cc: Blake, Jordan (ISS Atlanta)
Subject: Re: [DeleGate-En] http URL redirection and SSL
On 11/29/02(18:47) you "Blake, Jordan (ISS Atlanta)" <JBlake@iss.net> wrote
|Using DeleGate 8.1.0, SSLWAY works fine for me in CERN (RELAY=proxy) mode,
|but I'd like to be able to combine SSL with URL redirection
|(RELAY=delegate) using this notation https://delegate/-_-URL
|I can administer the proxy using https (https://delegate/-/admin/),
|but when I try to use the URL redirection it will work initially for a
|couple URLs, but fail after a few sites and then refuse to work after that,
|even sometimes after restarting DeleGate.
|I can't seem to reliably identify the problem.
|Also, URLs keep defaulting back to http:// instead of https:// when
|typed into the IExplorer address bar... don't know if that's something
|DeleGate has control of though.
If you are chaining DeleGate as tcprelay-DeleGate -> HTTPS-DeleGate
like describe in <URL:http://www.delegate.org/mail-lists/delegate-en/1981>,
then you need a parameter
at the HTTPS-DeleGate. Since RELAY=delegate makes DeleGate visible to
HTTP clients as it it is a origin server, the URL of DeleGate to be
shown by itself to client must be the one which clients identify the
DeleGate. Clients are seeing the URL (address) of tcprelay-DeleGate as
if it is the real HTTP-DeleGate server in this case.
@ @ Yutaka Sato <email@example.com> http://www.delegate.org/y.sato/
( - ) National Institute of Advanced Industrial Science and Technology (AIST)
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller