Lists Home |
Date Index |
At 7:41 PM -0500 1/5/04, Rich Salz wrote:
>Since you seem to have given this more than just casual thought, have
>you got ideas about a solution? To be explicit, the goals are:
> Authenticate clients
> Allow URL's to be cut/pasted amonng participants
> Limited exposure if packets are snooped
The solutions vary depending on the exact purpose. Restricting access
to password protected data is different from a shopping cart is
different from tracking users across sites. Except perhaps for the
latter, all can be solved without cookies. In all three cases (and
others) the user experience is improved without cookies.
In a truly individualized situation all that's needed are URLs of the
The username can also be stored in the path or authority component if
that's easier. e.g.
Note that the password is *not* transmitted in the URL. The server
requests the password using standard HTTP authentication mechanisms
and the client provides it in the standard way. Similarly other
information that is often stored in cookies--shopping cart contents,
path through a site, time of login, etc.--also need not be stored in
the URL. The server maintains this information as it does even with
cookies, at least in a secure system) and displays it to the user in
the content of the page. However, it need not show up in referrer
logs, browser location bars, and other such insecure places.
Not all use cases need this. For instance, if the site is merely
password protected but not customized per user (e.g. the W3C members
only pages) then the user name does not need to be part of the URI
because the page is not different for different users. But for each
different resource, there should be at least one URI. Cookie based
sites fail this test.
Elliotte Rusty Harold
Effective XML (Addison-Wesley, 2003)