Hi Travis:
I tried the same thing several months ago...
https:// protocol uses SSL encryption.
REBOL/core does not support (include) SSL since then REBOL/core would bloat
up to over 2 MEGS.
However, a work around is to use a redirector such as stunnel.
see http://www.stunnel.org for more info.
Other may be developing other work arounds...
Let us know how it works out for you.
-----Original Message-----
From: Travis Watkins [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 22, 2001 3:48 PM
To: [EMAIL PROTECTED]
Subject: [REBOL] HTTP Proxy to HTTPs
Does anyone know what is needed to make the HTTP proxy on www.rebol.org work
for HTTPs?
I can't seem to get past the CONNECT command.
I am trying to make a simple method for creating scripts for automated
access and processing of locations that require one or more levels of
authentification.
The HTTP works fine, I just write the Get commands out to a file delimited
with specific tags(<Request> and <End Request>), but I can't seem to get a
slightly modified copy to also run as a proxy for HTTPs.
(Modifications include changing the prot fom 80 to 443 and modification of
the parsing to accept CONNECT strings in addition to the Http Get strings.
The HTTP Proxy also identifies the simple Gif, Jpg, and Jpeg files so as not
to add them to the script(atleast the ones with only one "." in their file
name)
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
