Hi Dave, For information, were you able to solve this one? You should be able to authenticate your OPTIONS request like any other one.
Best regards, Jerome -- http://www.restlet.org http://twitter.com/#!/jlouvel -----Message d'origine----- De : davewilliamson [mailto:[email protected]] Envoyé : vendredi 27 août 2010 17:16 À : [email protected] Objet : Re: GWT RPC - Making comms secure... Just noticed that updates don't go to the mailing list, so I have posted a reply to my own message: UPDATE: Well, firstly I've found that I am doing the right thing, in fact it works beautifully!!! Except.... The reason it wasn't working previously was that I have the service setup with Basic Authentication, and it would appear that if the OPTIONS request is made whilst Basic Auth is required, it is the actual OPTIONS request that fails (it appears NOT to return the headers, although I need to confirm this!). So the questions have now change to: Is this by design, or is this a bug, or am I just doing something wrong? I really would prefer to have authenticated requests, rather than just leaving this wide open! Regards Dave -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/GWT-RPC-Making-comms-secure-tp5 469237p5469866.html Sent from the Restlet Discuss mailing list archive at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=26521 08 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2838444
