Michael Ströder wrote:
> Steve Holden wrote:
>
>>[EMAIL PROTECTED] wrote:
>>
>>
>>>It is not impossible though and in cases where you don't have a choice
>>>but to use a HTTP authentication scheme, use of AJAX may be the
>>>answer to still allowing use of a form based login scheme. See:
>>>
>>> h
Steve Holden wrote:
> [EMAIL PROTECTED] wrote:
>
>> It is not impossible though and in cases where you don't have a choice
>> but to use a HTTP authentication scheme, use of AJAX may be the
>> answer to still allowing use of a form based login scheme. See:
>>
>> http://www.peej.co.uk/articles/ht
[EMAIL PROTECTED] wrote:
> Steve Holden wrote:
>
>>[EMAIL PROTECTED] wrote:
>>Since HTTP authentication is managed by the browser it's difficult to
>>integrate it with web application authentication: basically you have to
>>choose between the two. There's no way for the server to tell the
>>browse
Steve Holden wrote:
> [EMAIL PROTECTED] wrote:
> Since HTTP authentication is managed by the browser it's difficult to
> integrate it with web application authentication: basically you have to
> choose between the two. There's no way for the server to tell the
> browser to start presenting the requ
[EMAIL PROTECTED] wrote:
> I have an apache 1.3.29 server that is running my website. I have
> written a bunch of scripts to generate the pages from csv files which
> work great.
>
> My next thing to learn is how to get user authentication functioning
> the way I need it.
>
> I understand the st
I have an apache 1.3.29 server that is running my website. I have
written a bunch of scripts to generate the pages from csv files which
work great.
My next thing to learn is how to get user authentication functioning
the way I need it.
I understand the steps required to make .htpaccess files wor
