 |  |
| |
Test the value of $_SERVER['HTTPS']:
if ('on' == $_SERVER['HTTPS']) {
print "The secret ingredient in Coca-Cola is Soylent Green.";
} else {
print "Coca-Cola contains many delicious natural and artificial flavors.";
}SSL operates on a lower level than HTTP. The web server and a browser negotiate an appropriately secure connection, based on their capabilities, and the HTTP messages can pass over that secure connection. To an attacker intercepting the traffic, it's just a stream of nonsense bytes that can't be read.
Different web servers have different requirements to use SSL, so check your server's documentation for specific details. No changes have to be made to PHP to work over SSL.
In addition to altering code based on $_SERVER['HTTPS'], you can also set cookies to be exchanged only over SSL connections. If the last argument to setcookie( ) is 1, the browser sends the cookie back to the server only over a secure connection:
/* set an SSL-only cookie named "sslonly" with value "yes" that expires
* at the end of the current browser session */
setcookie('sslonly','yes','','/','sklar.com',1);Although the browser sends these cookies back to the server only over an SSL connection, the server sends them to the browser (when you call setcookie( ) in your page) whether or not the request for the page that sets the cookie is over SSL. If you're putting sensitive data in the cookie, make sure that you set the cookie only in an SSL request as well. Keep in mind as well that the cookie data is unencrypted on the user's computer.
Recipe 8.2 discusses setting cookies; documentation on setcookie( ) at http://www.php.net/setcookie.
|  | |
| 14.10. Sharing Encrypted Data with Another Web Site |  | 14.12. Encrypting Email with GPG |
Copyright © 2003 O'Reilly & Associates. All rights reserved.