Re: request.remote_ip

2011-03-31 Thread Hemal Kuntawala
I had a similar problem with a Sinatra app on Rack. Rack's request.ip was returning Amazon LB IPs. I ended up grabbing the client IP from the env environment variables.. ip = env[‘HTTP_X_REAL_IP’] ||= env[‘REMOTE_ADDR’] Hope that helps. ( http://developerhemal.tumblr.com/post/3958107290/client-ip

Re: request.remote_ip

2011-03-31 Thread Brad Gyger
Looking into this now. I'll follow up with an email as well. On Mar 30, 11:23 am, kowsik wrote: > This is a bummer. We are about to switch to hostname-based SSL > onhttp://blitz.ioand it's important that we see the original IP. Can > someone from Heroku confirm/deny this and/or suggest a work a

Re: request.remote_ip

2011-03-31 Thread Jarin Udom
CloudFlare has the same problem, but they pass along an additional header you can use. Maybe Heroku can implement something like that. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To un

Re: request.remote_ip

2011-03-30 Thread kowsik
This is a bummer. We are about to switch to hostname-based SSL on http://blitz.io and it's important that we see the original IP. Can someone from Heroku confirm/deny this and/or suggest a work around? We are using sinatra and so far (without the SSL add-on) we can see the request.ip. Thanks, K.

Re: request.remote_ip

2011-03-30 Thread chris
Again, if you're using Hostname Based SSL, even on non-https requests, you will not get the users IP, no matter which headers you try. So, yeah, you'll have go to through a 3rd party, or try not to care about the IPs at all! -- You received this message because you are subscribed to the Google

Re: request.remote_ip

2011-03-25 Thread Travis Reeder
Did you try those headers? On Fri, Mar 25, 2011 at 1:28 PM, Carson Gross wrote: > OK, circling back on this: > > request.remote_ip > > Does *not* work consistently in our heroku application, even on non- > https requests. > > Any solutions or suggestions for this from t

Re: request.remote_ip

2011-03-25 Thread Carson Gross
OK, circling back on this: request.remote_ip Does *not* work consistently in our heroku application, even on non- https requests. Any solutions or suggestions for this from the heroku guys? I guess I can use clicky's API, but that would be a lot of work... Cheers, Carson On Mar 15, 9:

Re: request.remote_ip

2011-03-15 Thread marcel
I ran into this same problem playing with Rack::Bug. I couldn't access my site and determined it was because my client IP was not in the whitelist I'd configured. I read the Rails docs and even the source and it seemed like request.remote_ip should just work... but it clearly did not

Re: request.remote_ip

2011-03-15 Thread chris
... r just upgrade to ip-based SSL, it's way more expensive though. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@goo

Re: request.remote_ip

2011-03-15 Thread chris
Are you using Hostname Based SSL? Due to... who knows what... Hostname Based SSL will not allow you to get a users IP address. Instead, it will return the same few every time. Looking at different headers, etc. won't help. Sucks, I know. If you really need a users IP address, you can use an

Re: request.remote_ip

2011-03-14 Thread kowsik
tionController/AbstractRequest.html#M000235 > > It looks like request.remote_ip is actually smart-ish and tries to > resolve the original IP. > > I don't see an 'ip' method there (I've got to admit, I find the > standard ruby docs impenetrable.) > > Maybe the heroku load ba

Re: request.remote_ip

2011-03-14 Thread Carson Gross
Hmmm. Looking at the docs here: http://docs.huihoo.com/api/ruby-on-rails/classes/ActionController/AbstractRequest.html#M000235 It looks like request.remote_ip is actually smart-ish and tries to resolve the original IP. I don't see an 'ip' method there (I've got to admit,

Re: request.remote_ip

2011-03-14 Thread kowsik
On Mon, Mar 14, 2011 at 1:42 PM, Carson Gross wrote: >> >> Hello, >> >> I'm trying to get at the remote ip address for requests, and I'm using >> the standard >> >>  request.remote_ip >> >> method, but it appears that this is returning

Re: request.remote_ip

2011-03-14 Thread Carson Gross
arson Gross wrote: > > Hello, > > > I'm trying to get at the remote ip address for requests, and I'm using > > the standard > > >  request.remote_ip > > > method, but it appears that this is returning the same few IP's for > > all our users.  My

Re: request.remote_ip

2011-03-14 Thread Travis Reeder
Check out the headers, you may find X-Forwarded-For or X-Forwarded-Proto which will be the IP you want. On Mon, Mar 14, 2011 at 1:42 PM, Carson Gross wrote: > Hello, > > I'm trying to get at the remote ip address for requests, and I'm using > the standard > > reque

request.remote_ip

2011-03-14 Thread Carson Gross
Hello, I'm trying to get at the remote ip address for requests, and I'm using the standard request.remote_ip method, but it appears that this is returning the same few IP's for all our users. My guess is that this is the heroku load balancer at work, but that's just a sh