New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
express 2 not working #36
Comments
I'm having the same issue - and a similar one with the facebook example. |
Ditto. |
Same here |
Same here with GitHub auth. It still works but the server eventually locks up. |
i think your supposed to use res.end not res.send... |
res.end worked. |
I'm getting this with res.render but not with res.end |
Implemented in 0.3.0 |
Haven't tested, but thank you. |
I'm still having this issue as of 0.3.1 |
Which strategy.. I'm investigating an issue with the google strategy (google seem not to end their connections to json feeds anymore?) ... can you point me at your code at all ? |
The facebook strategy ... I'm not sure if I'm supposed to be trying to redirect in there and whether or not that's what is causing it ...
After thinking more about it ... what is likely going on here is that authenticate is sending the headers and I'm trying to add on to them with the redirect ... what is the suggested way to redirect after authenticating? I ended up replacing it with a javascript redirect. |
Ok. So presumably you want to call into loadAccount when a session first successfully authenticates? The best place to do this is over in your express/connect app or in some middleware... I'd like connect-auth to track first-authenticate and logout as a set of callbacks/events .. but as this doesn't currently exist you just need to do it yourself ... |
using the example twitter app, and express 2.0.0 and connect-auth 0.2.2
I'm getting the following from node 0.4.2:
The text was updated successfully, but these errors were encountered: