| |||||
| Important News! UserLand Software Acquires TLS | |||||
|
URLsThe secure web server is transparent. The HTTP headers are all there, and with the exception of the port number they're exactly the same as those provided by the traditional web server. Essentially, this means that anything which runs behind the standard web server will also run behind the secure server. However, it's up to you, the developer, to ensure that URLs generated by your scripts are correct. If a site is being served securely, URLs pointing to that site must start with "https:" instead of "http:".
Since the secure server really is transparent, we added a single flag variable, " For example:
If the secure server is running on a port other than the standard one (443 for HTTPS), you'll need to add that to the URL too, but the same is true for the traditional web server. For more information on this issue, see RFC: Port Forwarding Tool (from Eric Soroos). Last update: 4/4/2002; 12:45 AM |
||||
| © 2002 Macrobyte Resources. All rights reserved. | |||||