Web pages and input forms travel across the Internet in clear text. If your site displays or collects sensitive or personal information (e.g., credit card numbers) then you should have these pages secured with SSL encryption. To enable the secure HTML protocol (HTTPS) you will need a secure server certificate.

Secure Server Options

Usage Notes

• To secure one of your pages (e.g., an order form), you simply link to that page using a URL starting with  HTTPS:  instead of  HTTP: .
  If you are using our Shared VeriSign Certificate, then you link to your secure page using a URL starting with  HTTPS://secure.argos.net/[YourDomain]/ . (Replace [YourDomain] with your respective domain name.)
• All links to pictures, CGI or other scripts should be via a relative link, e.g., use  /images/picture.gif  instead of  http://www.lawyer.com/images/picture.gif.  Otherwise, your visitor will receive a warning that your page contains secure and unsecure contents.
• If you must link to pictures, CGI or other scripts on external sites, you must use a secure protocol, e.g., https://www.picturesource.com/images/picture.gif.  Otherwise, your visitor will receive a warning that your page contains secure and non-secure contents.
• If you are using a Self-Issued Certificate by Argos Network you should create a non-secure start page that invites visitors to accept and trust the Argos Networks certificate. This will avoid a warning that the certificate was issued by an untrusted authority.

• VeriSign
  Secure server certificates

domain name  ||  script library  ||  .asp samples  ||  secure server  ||  banners & icons
web site  ||  electronic mail  ||  newsgroups  ||  announcements

home  ||  search  ||  site info  ||  email  ||  usage conditions

This page was last updated on 08/01/99 12:46:43 AM.
© 1998, 1999,  H&M Systems Software,  Inc.