For tracking purpose, this question has led to the fix of a bug in the computation of HTTP Digest values. We now properly take into account request URIs different from the one used during the pre-initialization of the ChallengeResponse. The fix will ship in 2.0.10 and 2.1 RC1 today.
Thanks to Steve and ForgeRock for the help in resolving this issue. Best regards, Jerome -- http://www.restlet.org http://twitter.com/#!/jlouvel -----Message d'origine----- De : Steve Ferris [mailto:[email protected]] Envoyé : lundi 9 mai 2011 21:56 À : [email protected] Objet : Using HTTP Digest with multiple routes Hi, I've have HTTP DIGEST authentication working with my application, but I've a question around the best way of pre-initialising the ChallengeResponse objects. At the moment I seem to have to create a separate ChallengeResponse for each specific URI within the router since the verifier on server does an exact match on the URI. router.attach("/read", ReadResourceImpl.class); router.attach("/write", WriteResourceImpl.class); So on the client I need a ChallengeResponse for the ReadResourceImpl and a different one for WriteResourceImpl. Is there a way to create a single ChallengeResponse that can be used for all routes? regards Steve ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=27334 53 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2850120
