-
Notifications
You must be signed in to change notification settings - Fork 2k
Random port appended in OmniAuth callback? #227
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
Comments
Not sure. Could be a Facebook issue behind proxies. |
This looks related to #341 and you're getting the ephemeral port. |
trvsdnn
pushed a commit
to trvsdnn/node-http-proxy
that referenced
this issue
May 14, 2013
`req.remotePort' returns the ephemeral port, which is not useful. node v0.10.0 added `req.localPort' which returns what we want, but we want to maintain backwards compatibility. Fixes http-party#341 & http-party#227
No longer an issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using node-http-proxy with the following code:
Currently, this is breaking my omniauth for facebook. When I click "login with facebook" on my site,
I am 404'ed with the following url in my url bar:
Another attempt at this will produce port 49602. Which is extremely weird as I was testing my site on http://mysite.com. Where does the random port come from?
I have decided to test what is causing this, so I wget to see the url redirection:
If I remove the port from the url, I am actually able to login. Anyone know why I am seeing this random port being inserted into my url?
The text was updated successfully, but these errors were encountered: