Secure Transactions

The secure environment refers to the transmission of information from web browser to web server. If you have a link to an order form, for example, from your home page, you would need to use a URL similar to following:

https://wwwXX.hway.net/<userid>/form.htm (XX = server number) The "s" in https:// suggests an SSL related file. Substitute the path to the order form starting with user directory name. If your account resides on server #2, you would need to use https://www02.hway.net/<userid>/form.htm or 03, 04, etc. respectively depending on which server the secure form resides.

If the secure form calls a cgi script, you must also reference that script securely.

eg. <form method="post" action="https://wwwXX.hway.net/<userid>/cgi-local/order.cgi">

Retrieving Data From Server

As mentioned above, the secure environment refers to the transmission of information between web browser and web server. We suggest that you have a script written to save the submitted form content to a text file. In so doing, you can reference the text via secure URL and retrieve its content (eg. credit card information) securely via the web thus completing the loop.

eg. https://wwwXX.hway.net/<userid>/datafile.txt To protect the data from unauthorized web surfers, you can store the data file(s) in a password protected directory.

An alternative is to have the submitted form content sent to you via email. If your form references a custom script, you will need to reference the script securely. We have not implemented a solution for encrypting email.

Using cgiemail and SSL

If you are using cgiemail in conjunction with a secure form, you will need to reference the script (see below) and "success" URL securely. (The "success" URL is the web page you want to display after the email is successfully sent.)

<form method="post" action="https://wwwXX.hway.net/cgi-bin/cgiemail/<userid>/mailtemp.txt">