Authentication: multiple challenges?

Hi, According to RFC2616 section 14.47, it should be possible to have multiple challenges in a WWW-Authenticate header. I can't see a way to achieve that with Restlet. Is there a way? Context: I'm trying to protect a collection of resources with both HTTP Basic and a custom

Re: re servlet mapping question

Hi Ted, On Feb 28, 2008, at 5:11 PM, TA wrote: I'm not sure I follow your suggestion - if I remove the url mapping from the defaultAttach call, all URLs will map to the servlet/restlet and I don't want that because I have other servlets running the web container. What Stephan was pointing

Acegi support [was: AuthenticatedUser [was: Request in checkSecret()]]

Hi, Now all the logic specific to authentication schemes is delegated to the Engine. It will now be easy to add pluggable authentication modules. That's great to hear. Support Acegi http://restlet.tigris.org/issues/show_bug.cgi?id=264 The project for which I'm using Restlet uses Acegi

Re: Spring ServerServlet?

regards, Jerome -Message d'origine- De : Rhett Sutphin [mailto:[EMAIL PROTECTED] Envoyé : vendredi 25 janvier 2008 18:13 À : discuss@restlet.tigris.org Objet : Re: Spring ServerServlet? Hi, I'm a bit late to this party, but I've been playing around with another way of integrating Restlets

Re: PUT with no entity (architecture question)

Hi Rob, On Jan 14, 2008, at 12:13 AM, Rob Heittman wrote: I can't fault your design given your constraints. I think the general concept: identifying links with hierarchical URIs descending from the URI of each linked object, is at least a common idiom if not an established pattern. I

Re: PUT with no entity (architecture question)

Hi Rob, On Jan 14, 2008, at 9:50 AM, Rob Heittman wrote: 2.) Send a default entity body so the request goes through. I think this is the way to go, honestly, even if it lacks the purity Rhett is looking for. My interpretation of the spec is that an entity is required for a PUT I

PUT with no entity (architecture question)

Hi, I'm designing implementing my first REST-style API. It's for an existing application. I'm using Restlet 1.1-M1 and have found it very cleanly designed and easy to use. I've run into a problem where I can't seem to implement one of the resources in the way that makes most sense to

<    1   2