How Standard is "https:"?

Bill Frantz frantz@communities.com
Mon, 15 Mar 1999 17:43:25 -0800


At 05:21 PM 3/15/99 -0800, Mark S. Miller wrote:
>We are using "https:" for our download page
>https://www.cypherpunks.to/erights/download.html so that people will get
>it, and the downloads themselves, over what I assume to be an SSL
>connection.  However, "https:" isn't one of the URL protocol handlers built
>into java, and is therefore also currently missing from E.  How
>embarrassing -- we only support the insecure one!
>
>Also, various other tools seem not to recognize it.  For example, when I
>ask Dreamweaver to check for broken links in the erights site, it thinks
>the links to the download page are badly formed.  OTOH, Eudora seems happy
>with them.  So, how standard is "https:"?  What's Lynx do?

As far as I know, https: is the standard protocol identifier for SSL/TLS
(Transport Level Security, the IETF working group for SSL).  Now you know
the penetration for secure connections into the real world.  I believe that
the Cryptix people were working in the direction of having a Java SSL.