On Fri, 4 Nov 2005, Dave wrote:
> The standard authentication in Apache is pretty insecure
That's pretty unfair. Web authentication does what it says on the
tin: defines web credentials for access to access-controlled pages.
The underlying protocols quite deliberately did not implement
statefulness, and therefore in themselves do not define any kind of
"session". So it should come as no surprise that the concept of
logging-in and logging-out (which themselves imply some kind of
persistent session between these events) is not inherently present,
and has to be implemented "on top of" the existing protocols.
> is that it relies on the client to "forget" the username and
> password. So if you log into a site with basic authentication and
> keep the browser open, you have access forever.
For as long as those credentials are valid at the server, yes.
> Closing the browser usually ceases acces this, but as far as I can
> tell this is not forced in any way.
Client agents are certainly able to remember one or more sets of
credentials for a resource, and to try them again when challenged by
the server, yes.
Evidently this mechanism isn't the one that you're looking for, which
is fair enough if you've considered your requirements carefully;
although you should be aware that maintaining state, and making access
to resources conditional on that state, has its own implications, such
as the effect on cacheability, which can make access to pages
(particularly those which have to be re-created every time by
server-side processing) quite sluggish (I was in just such a situation
the other day, where even going Back to the previous page was taking
over 10 seconds while their server re-generated the uncacheable page
from scratch, which made things mighty tedious - I was glad to leave
a.s.a.p and buy the product from a competing vendor, whose web site
was much more responsive).
best regards
>> Stay informed about: Login page that supports "Logout" and times out.