The encrypted data contains more bytes than the raw data, increasing network transfer time. Other miscellaneous SSL handshaking for the life of the transaction. For these reasons SSL HTTP is slower and has far greater impact on the server system CPU than standard HTTP and therefore should only be used when transaction privacy is required, not as a general HTTP service. Also, if a general HTTP and an SSL HTTP service is provided on a multi-processor system, with one or other or both experiencing significant traffic, then the two services should be run in separate processes. Interoperability WASD SSL has been used against a wide variety of browsers and certificates.
Most combinations work.
Some do not, usually related to the level of encryption required by some certificates precluding export-grade browsers from connecting. To date OpenSSL certificates, and those from Thawte and VeriSign have been deployed on WASD servers. The example HTTPd startup procedure already contains support for the SSL executable. If this has been used as the basis for startup then only the respective boolean needs to be altered to use the SSL rather than the standard executable. The default port for an SSL service is 443.