Skip to content
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

Empty Response using Sample.js #36

Closed
paddycarver opened this issue May 23, 2011 · 8 comments
Closed

Empty Response using Sample.js #36

paddycarver opened this issue May 23, 2011 · 8 comments

Comments

@paddycarver
Copy link

I get the distinct feeling I'm doing something incredibly stupid, but I can't seem to get this to do anything. I run sample.js, and pull it up. I fill in https://www.google.com/accounts/o8/id, as per the Google spec (http://code.google.com/apis/accounts/docs/OpenID.html#endpoint). I then get infinite loading, followed by the server giving me an empty response.

Is this a bug? Am I just an idiot?

@havard
Copy link
Owner

havard commented May 24, 2011

You need to change the verification URL in sample.js to match your setup. The default URL in sample.js is http://example.com/verify, which I suspect doesn't do much for you unless you happen to be running your sample.js on port 80 of example.com. :)

@havard havard closed this as completed May 24, 2011
@paddycarver
Copy link
Author

I've done that, to the same result. I mean, I never even get redirected to the endpoint. I don't think discovery ever occurs. Is it possible the GET request for discovery doesn't have an Accept header for "application/xrds+xml"? Is there any internal logging mechanism I can activate to figure out where my discovery is failing? I have a sinking feeling this is my own stupid fault, with a server mis-configuration or something.

@paddycarver
Copy link
Author

Poking around a bit, it seems as though https.get never emits an 'end' event. I'm on 0.5.0-pre. Any thoughts?

@havard
Copy link
Owner

havard commented May 24, 2011

That was an issue with node earlier (back in 0.4.0). If this has reappeared in 0.5-pre, please report it to the node guys.

@paddycarver
Copy link
Author

Whoa, quick response. Will look into it, thanks. :)

@paddycarver
Copy link
Author

Looks like this is an issue in 0.4.8, as well. Do you know which versions of node this module works with?

@havard
Copy link
Owner

havard commented May 24, 2011

I can confirm it works on 0.4.1.

@paddycarver
Copy link
Author

Awesome, thanks for the info. I'll have to keep an eye on it to see if the bug gets patched in later versions of node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants