In message <_A491@delegate-en.ML_> on 06/11/99(02:35:50)
you "Eichert, Diana" <firstname.lastname@example.org> wrote:
|First, thankyou for work you have done on delegate.
|I run the following command as suggested on the Delegate SSL page to allow
|DeleGate as a http proxy which make a bare HTTP client be a HTTPS/SSL
|delegated -v -P8080 CMAP="sslway -co:FSV:https:*:*"
|Then I remember that it is on the otherside of a proxy server so I change
|the command to:
|delegated -v -P8080 PROXY="wwwproxy.sandia.gov:80:*" CMAP="sslway
|06/10 11:30:42.76  1+1: REQUEST = GET http://secureweb.sandia.gov/
|Why is it not requesting "https://secureweb.sandia.gov/" ?
It should be requested by the bare HTTP client connecting to DeleGate
(which is acting as a proxy server of HTTP in your example)
|Am I misunderstanding the purpose of "DeleGate as a http proxy which make a
|bare HTTP client be a HTTPS/SSL client:"?
Ancient NCSA-Mosaic is one of such bare HTTP clients which utilizes
HTTPS/HTTP gateway when it is given an environment variable
You can simulate such a bare HTTP client using telnet client like this:
% telnet delegate-host 8080
GET https://secureweb.sandia.gov/ HTTP/1.0
In your example, Mozilla cannot be set up to act as a bare HTTP client
which forward HTTPS/SSL protocol as is to a HTTP proxy. But if you
intend to access to "https://secureweb.sandia.gov/*" as if it is
"http://secureweb.sandia.gov/*" via DeleGate as a HTTP proxy (I don't
understand if such proxy has practical meaning), you can do it adding
the following parameter:
Anyway I feel it difficult to suggest an appropriate usage of SSLway
without knowing why you need it to solve what kind of problem.
Yutaka Sato <email@example.com> http://www.etl.go.jp/~ysato/ @ @
Computer Science Division, Electrotechnical Laboratory ( - )
1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan _< >_