Adam Taft wrote:
Peter Lacey wrote:
In that I agree. But in my scenario the client of the "authenticate
service" is the resource being accessed, not the client requesting
the resource. Visually:
CLIENT -- uname/pwd ---> RESOURCE -- uname/pwd --->
AUTH
I think we're having some nomenclature issues. See inline for more.
Adam Taft wrote:
Peter Lacey wrote:
he wants to provide a RESTful means of having the service validate
the credentials. At least that's how I read it.
Right, I understand that. What I'm saying is tha
I think you might be missing the point of JC's original request. It's
not that he wants to provide some new means of authenticating to a
service, he wants to provide a RESTful means of having the service
validate the credentials. At least that's how I read it.
In other words, a client can au
body of the POST as opposed to parameters within a
URL.
Mitch
> -----Original Message-
> From: Peter Lacey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 02, 2007 2:55 PM
> To: discuss@restlet.tigris.org
> Subject: Re: Restful Login/Identifier
>
> I have only just start
contents are not encrypted via SSL, only the
payload of the request? I think that's why Basic Authentication sends
the data inside the body of the POST as opposed to parameters within a
URL.
Mitch
-----Original Message-
From: Peter Lacey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, Oc
I have only just started mussing over the very same idea. In my
thinking the URLs would be much more readable. The core user resource
would be something like http://example.com/users/{uname} To use this
for authentication purposes, an application would receive credentials
from the user, and
Sorry to keep responding to my own posts, but it turns out that the
problem existed between chair and keyboard. Restlet's working dandy.
Pete
Peter Lacey wrote:
All,
I have a resource for which I'm generating a strong ETag and a
Last-Modified header. I first GET the resource w
All,
I have a resource for which I'm generating a strong ETag and a
Last-Modified header. I first GET the resource without any conditions
(no If-None-Match and no If-Modified-Since). I next GET it again
supplying the ETag and get a 304 response as appropriate. I then update
the resource an
changes the observed behavior a bit, it should only go in
Restlet 1.1,
IMHO.
Best regards,
Jerome
-Message d'origine-
De : Stian Soiland [mailto:[EMAIL PROTECTED] Envoyé
: mercredi
6 juin 2007 11:23
À : discuss@restlet.tigris.org
Objet : Re: Conditional GETs?
On 4 Ju
, doc);
result.setTag(new Tag([your etag], false));
}
return result;
}
Peter Lacey wrote:
Hi,
I'm new to RESTlet and trying to create a resource that supports
conditional gets (ETag, Not Modied). So far I have the normal GET done,
I can attach an ETag to the representation, I c
Hi,
I'm new to RESTlet and trying to create a resource that supports
conditional gets (ETag, Not Modied). So far I have the normal GET done,
I can attach an ETag to the representation, I can see how to get the
conditions from the client request, and I can see how to send back a
304. But for
11 matches
Mail list logo
