the location of a page through the properties.
Being able to view the URL in the location bar is useful, but is it strictly
necessary?
Regards,
Willem Jan
-Original Message-
From: oauth@googlegroups.com [mailto:oa...@googlegroups.com] On Behalf Of
Paul Osman
Sent: Sunday, January
, Paul Osman p...@eval.ca wrote:
Hi Willem,
While it's obviously not something that is covered in the spec (User-Agent
specific details are understandably out of scope), I would say that it is
strictly necessary. It gets into the spirit vs the letter of a
specification. In my view, using
If the user cannot reliably see who is presenting the authorization-sign in
window, they have no idea who they are giving their credentials to. This makes
the whole point of delegated authorization moot, so I would consider it
absolutely necessary to direct the user to a browser window where
Hi Florent,
I certainly couldn't see anything in the spec that addresses sending
OAuth parameters using a combination of GET, POST or Authorization
headers.
While I certainly think that it's a strange thing to do (seems like
more work for the Consumer Developer), I think as a Service
Hi Jared,
You'll probably want to try the Google Accounts API Google Group:
http://groups.google.com/group/Google-Accounts-API
This list is generally for discussion of the OAuth protocol and not
specific implementations.
Cheers,
--
Paul Osman
On 14-Sep-09, at 12:21 PM, Jared wrote
