<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.williams-http-rest-auth" target="https://datatracker.ietf.org/doc/html/draft-williams-http-rest-auth-03">
   <front>
      <title>RESTful Authentication Pattern for the Hypertext Transport Protocol (HTTP)</title>
      <author initials="N." surname="Williams" fullname="Nicolás Williams">
         <organization>Cryptonector</organization>
      </author>
      <date month="August" day="15" year="2012" />
      <abstract>
	 <t>   This document proposes a &quot;RESTful&quot; pattern of authentication for
   HTTP/1.0, 1.1, and 2.0.  The goal is to make it easy to add
   authentication mechanisms to HTTP and to make it easy to implement
   them even without much help from the HTTP stack (though it is best to
   integrate authentication into the stack, of course).

   Among other benefits of RESTauth: it is orthogonal to &quot;HTTP routers&quot;
   and proxies, it results in session Uniform Resource Identifiers
   (URIs) that can be DELETEd to logout, naturally supports multi-legged
   authentication schemes, and it can be universally implemented on the
   server side with the Common Gateway Interface (CGI) and FastCGI.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-williams-http-rest-auth-03" />
   
</reference>
