This is actually expected behavior. If you access the resource again but removing the code you will be able to access it, the problem is that it tries to generate a token from an old code. We are working on removing the code once the authorization is complete but that requires an additional redirect. Another thing you also might want to consider is to save your token so it is not regenerated in every request. If you like I can provide some useful code for this.
cheers, martin ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2799070
