Hi Michiel,
shouldn't the revocation POST request work fine with CORS? Or is there
something we need to specify in order to make it work?
best regards,
Torsten.
Am 27.05.2012 13:20, schrieb Michiel de Jong:
awesome! just that - first thing that catches the eye right when you
skim the table of contents is:
why did you use JSONP instead of its CORS? You can read more about CORS here:
http://enable-cors.org/
http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#CORS_relationship_to_JSONP
On Sun, May 27, 2012 at 10:41 AM,<internet-dra...@ietf.org> wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol Working Group of
the IETF.
Title : Token Revocation
Author(s) : Torsten Lodderstedt
Stefanie Dronia
Marius Scurtescu
Filename : draft-ietf-oauth-revocation-00.txt
Pages : 6
Date : 2012-05-26
This draft proposes an additional endpoint for OAuth authorization
servers for revoking tokens.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-oauth-revocation-00.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-oauth-revocation-00.txt
The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-oauth-revocation/
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
