Warning: Table './jdarx_drupal/sessions' is marked as crashed and should be repaired query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = '8823380a4581d3217f1cc16506f8fa31' in /f2/jdarx/public/includes/database.mysql.inc on line 172

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /f2/jdarx/public/includes/database.mysql.inc:172) in /f2/jdarx/public/includes/bootstrap.inc on line 899

Warning: Cannot modify header information - headers already sent by (output started at /f2/jdarx/public/includes/database.mysql.inc:172) in /f2/jdarx/public/includes/bootstrap.inc on line 531

Warning: Cannot modify header information - headers already sent by (output started at /f2/jdarx/public/includes/database.mysql.inc:172) in /f2/jdarx/public/includes/bootstrap.inc on line 532

Warning: Cannot modify header information - headers already sent by (output started at /f2/jdarx/public/includes/database.mysql.inc:172) in /f2/jdarx/public/includes/bootstrap.inc on line 533

Warning: Cannot modify header information - headers already sent by (output started at /f2/jdarx/public/includes/database.mysql.inc:172) in /f2/jdarx/public/includes/bootstrap.inc on line 534
HTTP Authentication: Solutions and Futures Introduction | wayland's Computer Stuff

HTTP Authentication: Solutions and Futures Introduction

warning: Cannot modify header information - headers already sent by (output started at /f2/jdarx/public/includes/database.mysql.inc:172) in /f2/jdarx/public/includes/common.inc on line 141.

There are various problems with HTTP authentication. In this series I discuss the various problems and their solutions.

Introduction

Many have cited problems with HTTP authentication (as opposed to session-based authentication, which has its own problems).

Problems often cited include:

  1. Authentication Is Not Optional
  2. User Interface
    1. Discontinuity with site theme makes interface jarring
    2. Username prompt may confuse the user
    3. Not obvious what to do if you forgot your password
    4. Not obvious what to do if you don't have an account
  3. No Logout facilities
  4. Difficult to do single-sign on
  5. Lack of Internationalisation
  6. Poor software support

Descriptions of these problems and related solutions are in the articles linked below.

Background reading

Since REST fans like HTTP Authentication, I present a link to a REST book, as well as to a HTTP book.

Additional reading

While not really part of this series, the article HTTP 1.2 -- What it needs is related.