Yes, yes. I don't see why you'd want to use DELETE or PUT for the request token or access token endpoints. Is there an argument for supporting them? Otherwise this thread is just silly.
Leah On Wed, Apr 29, 2009 at 12:29 PM, Jesse Myers <[email protected]> wrote: > > We did something similar to allow DELETE to be used to revoke an > access token (though we also supported POST). However, this was a > protected resource request, not a request token or access token > endpoint. > > jesse > > On Wed, Apr 29, 2009 at 11:30 AM, Leah Culver <[email protected]> > wrote: > > Pownce used DELETE to let a consumer application revoke a token on behalf > of > > a user. It's not really a typically thing to do though. > > > > Leah > > > > On Wed, Apr 29, 2009 at 3:38 AM, [email protected] > > <[email protected]> wrote: > >> > >> From my reading of the spec it doesn't stop a SP from specifying > >> requireing the use of the PUT or DELETE http methods (though why you > >> would use delete I do not know) for the request token and access token > >> end points. > >> > >> Can anyone see any cases where this would be done or do you think > >> there is an argument for just supporting POST and GET? > >> > >> Thanks > >> > >> Chris. > >> > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
