I am attempting to use the Google AdWords API which requires a PECL
extension for OAuth 1 to work. Because I'm using GoDaddy I'm a bit limited.
Can anyone thing of a way around this? Here is the error message I am
getting when trying to interact with the API:
*Fatal error*: Uncaught exception '
ch so it's
accepted let me know.
On May 7, 11:14 am, John Kristian wrote:
> Thank you for the patch. I'll review it this weekend.
>
> It's nice to hear you're getting some value from this software.
>
> On May 5, 7:32 pm, Matt wrote:
>
> > I opened issu
I opened issue 156 a couple of weeks ago, including a patch to fix the
problem. There hasn't been activity on the bug, so I'm not sure if
anybody has looked at it.
Is there a procedure I should follow to get my issue and patch
reviewed, and hopefully accepted into the mainline OAuth Java library?
etting close!
Turns out that for .NET solutions you need to set
System.Net.ServicePointManager.Expect100Continue = false; (http://
blogs.msdn.com/shitals/archive/2008/12/27/9254245.aspx)
regards,
Matt
On Jan 27, 5:00 pm, Matt wrote:
> I hate to continue replying to my own post, but I
the rest in the query string (from inside FireBug in-browser).
I'm at my wits end on this one - obviously the only error that we can
expect is "unauthorized", but there are *so* many things that can go
wrong in the signing/request process in OAuth that I might as well
throw a dart w
or the full request URL (minus any querystring)?
regards,
Matt
On Jan 27, 2:51 pm, Matt wrote:
> I am trying to create an OAuth consumer. Instead of testing it
> against my own (likely incorrectly implemented) oauth service
> provider, I decided to test it against an established OAu
doesn't let you customize all the input parameters.
regards,
Matt
--
You received this message because you are subscribed to the Google Groups
"OAuth" group.
To post to this group, send email to oa...@googlegroups.com.
To unsubscribe from this group, send email to
oauth+unsubscr
ing for
the original request-token), and why is the 3rd combined with the
consumers secret to sign resource-requests (instead of just the
consumer secret)?
regards,
Matt
--
You received this message because you are subscribed to the Google Groups
"OAuth" group.
To post to this group, send e
Hello there,
I've used http://documentation.fring.com/images/1/11/Oauth_diagram.png
to explain OAuth a few times. The image requires some explanation
usually but it covers the details.
Thanks;
— Matt Sanford
On Nov 2, 2009, at 4:42 AM, Mr. Schtief wrote:
>
> Hi,
>
> I&
If you read my blog entry (listed below) on how I did this, I used a
ProxyServlet to get around the SOP in browsers.
http://raibledesigns.com/rd/entry/implementing_oauth_with_gwt
Matt
On Sat, Jun 20, 2009 at 4:22 PM, John Kristian wrote:
>
> Can a GWT application communicate cross-domain
orize it. After that,
it seems like getting an access_token works 50% of the time and
calling the api (with auth_token as a param in the URL) works 30% of
the time.
Thanks,
Matt
On Jun 17, 10:11 pm, Chirag Shah wrote:
> Hey Matt, try the code below. It works reliably for me.
>
> Make sure yo
locString += paramList[x] + "&";
}
return baseStr[1][0] + "?" + locString.slice(0,
locString.length - 1);
};
Any idea why this could be happening?
Thanks,
Matt
--~--~-~--~~~---~--~~
You received this messag
missed the early on discussions. I'll read back in the
group some for more history.
— Matt
On May 1, 2009, at 1:44 PM, Jonathan Sergent wrote:
> Let me additionally say that this discussion is dangerous and voting
> is no way to design a protocol. What are the arguments in favo
it or leave it.
Thanks;
— Matt Sanford
On May 1, 2009, at 10:39 AM, Eran Hammer-Lahav wrote:
>
> I think the discussion around the version number is completely
> misguided because we don't have a basic agreement on what the hell
> the version is even for. This means that
Option 3 … that's what versions are for, incrementing.
On May 1, 2009, at 1:25 AM, Blaine Cook wrote:
>
> We need to build some consensus around the version preference. As I
> see it, there are several options:
>
> 1. "1.0 Rev A" with no version string change (i.e., oauth_version=1.0)
> 2. "1.0a
callback_token prevents
other man-in-the-middle style attacks after the user has been returned
to the consumer app. Does this sound like what you're suggesting?
Thanks;
– Matt Sanford / @mzsanford
Twitter API Developer
On Apr 23, 2009, at 10:16 AM, Mike Malone wrote:
>
Hi Mark,
It looks like your java-twitter-0.9-SNAPSHOT.jar was built with
Java 1.6 and you're currently compiling under Java 1.5. You either
need a jar that works with Java 1.5 or you need to compile your
project with Java 1.6.
Thanks;
— Matt Sanford / @mzsanford
On Apr 21,
17 matches
Mail list logo
