-
Notifications
You must be signed in to change notification settings - Fork 101
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
Comments
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. :) |
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. |
Poking around a bit, it seems as though https.get never emits an 'end' event. I'm on 0.5.0-pre. Any thoughts? |
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. |
Whoa, quick response. Will look into it, thanks. :) |
Looks like this is an issue in 0.4.8, as well. Do you know which versions of node this module works with? |
I can confirm it works on 0.4.1. |
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. |
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?
The text was updated successfully, but these errors were encountered: