HTTPS and Drupal

By

This article was published in the print magazine Drupal Watchdog, Volume 2 Issue 2, 2012-08, on page 7, by Tag1 Publishing. The magazine was distributed at DrupalCon Munich, 2012-08-20.

There are countless reasons why any given website should support the use of the HTTP Secure protocol (indicated in URLs with the protocol-and-connection prefix "https://"). If visitors to your website will be submitting confidential information — such as credit card numbers — in web forms, then the connections between the visitors' computers and the web server should be encrypted using HTTPS. The Drupal community documentation includes a page with helpful information for properly configuring your web server and Drupal itself.

Drupal padlock
Figure 1. Drupal padlock

Copyright © 2012 Michael J. Ross. All rights reserved.

Add new comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <address> <area> <blockquote> <br> <cite> <code> <dd> <div> <dl> <dt> <em> <fieldset> <h1> <h2> <h3> <h4> <h5> <h6> <hr> <img> <input> <li> <map> <ol> <p> <pre> <span> <strong> <sup> <u> <ul>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
5 + 6 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.