Roxen.git / server / modules / examples / auth.pike

version» Context lines:

Roxen.git/server/modules/examples/auth.pike:2:   inherit "module";   // All roxen modules must inherit module.pike      // Some defines for the translation system   //   //<locale-token project="mod_auth">LOCALE</locale-token>   #define LOCALE(X,Y) _DEF_LOCALE("mod_auth",X,Y)   // end of the locale related stuff       - constant cvs_version = "$Id: auth.pike,v 1.4 2000/11/27 06:17:12 per Exp $"; + constant cvs_version = "$Id: auth.pike,v 1.5 2000/12/02 19:26:10 per Exp $";   constant module_type = MODULE_AUTH;   LocaleString module_name_locale = LOCALE(1,"RefDoc for MODULE_AUTH");   LocaleString module_doc_locale =    LOCALE(2,"This module does nothing, but its inlined documentation "    "gets imported into the roxen programmer manual. You definetely "    "don't want to use this module in your virtual servers, since "    "anybody with access to your admin interface or server configuration "    " file automatically gains access to all yourpasswords. For a "    " budding roxen programmer, the module however does show the "    " basics of making an authentication module.");      void create()   {    defvar("users", Variable.StringList(({}), VAR_INITIAL,    LOCALE(3,"Users and Passwords"),    LOCALE(4,"A list of username:password "    "pairs the module should grant " -  "access for.")); +  "access for.")));   }      array|int auth(array(string) auth, RequestID id)   //! The auth method of your MODULE_AUTH type module is called when the   //! browser sent either of the <tt>Authorization</tt> or   //! <tt>Proxy-Authorization</tt> HTTP headers (see RFC 2617).   //!   //! The auth argument passed is calculated as header_content/" ", but   //! where the second element is base64-decoded (meaning that you won't   //! need to do so yourself). A typical auth array you might receive