Hi Lauri, Thanks for sharing this workaround.
The current code sets the user and password given in ChallengeResponse on the internal RequestBuilder that is used: http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/gwt/http /client/RequestBuilder.html#setPassword%28java.lang.String%29 Let's keep an eye on it. I suggest entering a bug report for it with your detailed environment: http://www.restlet.org/community/issues Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : webp...@tigris.org [mailto:webp...@tigris.org] Envoyé : vendredi 24 juillet 2009 12:12 À : discuss@restlet.tigris.org Objet : RE: GAE + GWT + Restlet 2.0 M3 + challenge response is null on server side Hi Jerome, I made a workaround for this. I'm adding the authorization header manually when building a Request using the following code: Series<Parameter> headers = new Form(); headers.add("Authorization", "Basic " + base64EncodedCredentials); request.getAttributes().put("org.restlet.http.headers", headers); Adding Authorization header by hand was prohibited in HttpConverter, so I had to remove the authorization header check from there. Best, Lauri ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23751 46 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2375493
