jdolitsky / AppDotNetPHP

PHP library for the App.net Stream API
34 stars 19 forks source link

setSession() ? #11

Closed adamjgrant closed 11 years ago

adamjgrant commented 11 years ago

I'm using some of the basic code on the readme as well as the core appdotnet.php files.

It keeps going through a redirect loop. It looks as though the function setSession is never actually called, however. So the cookies don't get set and thus the loop is created. I'll see if I can fix this and put in a PR.

kohlmannj commented 11 years ago

Having a similar problem, and I have no idea. I temporarily removed the redirect in callback.php and saw that PHP output an "Undefined Offset" error:

Notice: Undefined offset: 1 in /Library/WebServer/Documents/AppDotNetPHP/AppDotNet.php on line 155

Here's line 155:

list($headers,$content) = explode("\r\n\r\n",$response,2);

So is it something with explode()? Evidently.

jdolitsky commented 11 years ago

I'm not having these issues. Can you explain your implementation further? @kohlmannj try commenting out line 196 of AppDotNet.php if your not using rate limiting data for now. We will try to look into this. @ajkochanowicz Are you using the same gateway page as your callback/redirect? This may create an issue depending on your code

ravisorg commented 11 years ago

I would expect the problem is the result you're getting back has no body, just an http header. I'll take a look as soon as I can...

jdolitsky commented 11 years ago

im running linux, possibly a mac config thing w/ curl?

jdolitsky commented 11 years ago

okay. just made some changes, check out the read-me. please try the new version (EZAppDotNet) and let me know if the error still occurs

kohlmannj commented 11 years ago

Will do, Josh. Thanks a bunch! Just got home from work, so I'll check it out in a bit.

– Joe

On Aug 26, 2012, at 5:17 PM, Josh Dolitsky notifications@github.com wrote:

okay. just made some changes, check out the read-me. please try the new version (EZAppDotNet) and let me know if the error still occurs

— Reply to this email directly or view it on GitHub.