HTTP Digest Authentication - Lift

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Lift
Message from discussion HTTP Digest Authentication
Received-SPF: pass (google.com: domain of d...@athena.com designates 64.27.11.181 as permitted sender) client-ip=64.27.11.181;
Message-ID: <4917AF05.7040800@athena.com>
Date: Sun, 09 Nov 2008 19:48:21 -0800
From: David Pollak <d...@athena.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="------------060204020107040509040900"
To: liftweb@googlegroups.com
Subject: Re: [Lift] Re: HTTP Digest Authentication
References: <c16f7be8-52c9-4a3c-b62f-bb3cbaf0cca0@b2g2000prf.googlegroups.com>  <cdbebedf0811090549v17769cc4n900f5fca1cca8419@mail.gmail.com>  <bdd2e7ee-ce2e-4a7b-b563-87ce171c765b@n1g2000prb.googlegroups.com>  <cdbebedf0811090600p5d378cc8qce7f375cee5a2306@mail.gmail.com>  <a6ad6f5f-c905-45b4-b655-4209eb4d95cc@o40g2000prn.googlegroups.com>  <cdbebedf0811090627u3adcce29r3ce40c4fbf561995@mail.gmail.com>  <e6d3ec4c-1dbf-4766-985b-cda3b1d5c83d@a29g2000pra.googlegroups.com>  <ff3d96ec-2e8e-4113-85d3-390e08273941@d36g2000prf.googlegroups.com>  <cdbebedf0811091145n7cd76575mafbc5d3cbfc7ec63@mail.gmail.com> <fb064997-db6a-4458-b752-7ab1e0688b75@f37g2000pri.googlegroups.com>
In-Reply-To: <fb064997-db6a-4458-b752-7ab1e0688b75@f37g2000pri.googlegroups.com>

--------------060204020107040509040900
Content-Type: text/plain; charset=ISO-8859-1



Tim Perrett wrote:
> Hey David,
>
> I've been doing some noodling and think I have a good scheme to
> implement this. I'll make a branch on github and then post to the list
> when my alterations are ready.
>   
Please do not do this.

Please write a stand-alone app before committing anything into Lift, 
example or otherwise.

> Cheers
>
> Tim
>
> PS: sorry for my high-volume posting in a stream-of-consciousness
> style! Its part of my process ;-)
>
> On Nov 9, 7:45 pm, "David Pollak" <feeder.of.the.be...@gmail.com>
> wrote:
>   
>> On Sun, Nov 9, 2008 at 8:08 AM, Tim Perrett <he...@timperrett.com> wrote:
>>
>>     
>>> One other thought on this, if no credentials are found, wouldn't it be
>>> best to challenge the requester with a 401, but with the www-
>>> authenticate header or something? Rather than just providing a plain
>>> 401?
>>>       
>>> Perhaps this could be wrapped up in
>>> DigestAuthenticationChallengeResponse or something?
>>>       
>> Steps:
>>
>>    1. Get something running in a stand-alone app
>>    2. Roll the example into sites/example
>>    3. Refactor the example code into core Lift stuff
>>
>> Thanks,
>>
>> David
>>
>>
>>
>>     
>>> Cheers, Tim
>>>       
>> --
>> Lift, the simply functional web frameworkhttp://liftweb.net
>> Collaborative Task Managementhttp://much4.us
>> Follow me:http://twitter.com/dpp
>> Git some:http://github.com/dpp
>>     
> >
>   

--------------060204020107040509040900
Content-Type: text/html; charset=ISO-8859-1

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Tim Perrett wrote:
<blockquote
 cite="mid:fb064997-db6a-4458-b752-7ab1e0688...@f37g2000pri.googlegroups.com"
 type="cite">
  <pre wrap="">Hey David,

I've been doing some noodling and think I have a good scheme to
implement this. I'll make a branch on github and then post to the list
when my alterations are ready.
  </pre>
</blockquote>
Please do not do this.<br>
<br>
Please write a stand-alone app before committing anything into Lift,
example or otherwise.<br>
<br>
<blockquote
 cite="mid:fb064997-db6a-4458-b752-7ab1e0688...@f37g2000pri.googlegroups.com"
 type="cite">
  <pre wrap="">
Cheers

Tim

PS: sorry for my high-volume posting in a stream-of-consciousness
style! Its part of my process ;-)

On Nov 9, 7:45&nbsp;pm, "David Pollak" <a class="moz-txt-link-rfc2396E" href="mailto:feeder.of.the.be...@gmail.com">&lt;feeder.of.the.be...@gmail.com&gt;</a>
wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">On Sun, Nov 9, 2008 at 8:08 AM, Tim Perrett <a class="moz-txt-link-rfc2396E" href="mailto:he...@timperrett.com">&lt;he...@timperrett.com&gt;</a> wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">One other thought on this, if no credentials are found, wouldn't it be
best to challenge the requester with a 401, but with the www-
authenticate header or something? Rather than just providing a plain
401?
      </pre>
    </blockquote>
    <blockquote type="cite">
      <pre wrap="">Perhaps this could be wrapped up in
DigestAuthenticationChallengeResponse or something?
      </pre>
    </blockquote>
    <pre wrap="">Steps:

&nbsp; &nbsp;1. Get something running in a stand-alone app
&nbsp; &nbsp;2. Roll the example into sites/example
&nbsp; &nbsp;3. Refactor the example code into core Lift stuff

Thanks,

David



    </pre>
    <blockquote type="cite">
      <pre wrap="">Cheers, Tim
      </pre>
    </blockquote>
    <pre wrap="">--
Lift, the simply functional web frameworkhttp://liftweb.net
Collaborative Task Managementhttp://much4.us
Follow me:<a class="moz-txt-link-freetext" href="http://twitter.com/dpp">http://twitter.com/dpp</a>
Git some:<a class="moz-txt-link-freetext" href="http://github.com/dpp">http://github.com/dpp</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--------------060204020107040509040900--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
