Did you try those headers? On Fri, Mar 25, 2011 at 1:28 PM, Carson Gross <[email protected]> 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 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:39 am, marcel <[email protected]> wrote: > > 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_ipshould just work... but it clearly did not. I logged > > all the request object's properties and saw my client IP in there, but > > for whatever reason request.remote_ipalways returned Heroku's load > > balancer's IP and not my real client IP. > > > > In the end I side-stepped the problem and just setup a password for > > access. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
