Anything new with this? I have an app which is complete behind SSL
(hostname SSL) and we have to implement IP logging. Do we need to
change/upgrade our ssl service ?
On Oct 5, 1:26 pm, marcel wrote:
> Or just
>
> request.env.ip
>
> http://rack.rubyforge.org/doc/classes/Rack/Request.src/M000288.ht
Or just
request.env.ip
http://rack.rubyforge.org/doc/classes/Rack/Request.src/M000288.html
On Oct 2, 11:55 am, Peter van Hardenberg wrote:
> I use this in my code -- I run my apps at foo.heroku.com with whatever
> the ghetto SSL option is, so YMMV.
>
> def remote_ip
> if forwarded = reque
I use this in my code -- I run my apps at foo.heroku.com with whatever
the ghetto SSL option is, so YMMV.
def remote_ip
if forwarded = request.env["HTTP_X_FORWARDED_FOR"]
forwarded.split(",").first
elsif addr = request.env["REMOTE_ADDR"]
addr
end
end
-pvh
On Oct
My assumptions on using hostname SSL:
1. You can't collect IPs for the subdomain you are tying your SSL to
using hostname SSL (for reasons outlined below)
2. You can collect IPs for the parts of your app that are non-SSL if
you use a different subdomain/root. Example: secure.myapp.com for SS
I am looking at the following headers in my Heroku apps. Not all of
them get set. All of them can be faked (as far as I know).
request.env['HTTP_CLIENT_IP']
request.remote_ip
request.env['HTTP_X_FORWARDED_FOR']
request.env['REMOTE_ADDR']
Paul
On Sep 28, 2:45 am, Josh K wrote:
> Hi Guys,
>
> We
Still is a problem if you're using the "Hostname Based Custom SSL" --
in order to get the users IP address, you'll have to use "IP Based
Custom SSL" and pay $80 more per month :(
On Sep 29, 1:44 pm, Keenan Brock wrote:
> This used to be a problem with ssl.
> Don't think it has been resolved
>
> -
This used to be a problem with ssl.
Don't think it has been resolved
--Keenan
On Sep 29, 2010, at 1:38 PM, Aaron Brethorst wrote:
> I haven't tried this with Heroku, but with another app I had hosted on EC2 I
> was able to use request.env['HTTP_X_FORWARDED_FOR'] to get this.
>
> On Sep 28, 201
I haven't tried this with Heroku, but with another app I had hosted on EC2 I
was able to use request.env['HTTP_X_FORWARDED_FOR'] to get this.
On Sep 28, 2010, at 2:45 AM, Josh K wrote:
> Hi Guys,
>
> We have a web app deployed on Heroku which requires ip address logging
> of each request, but w
Hi Guys,
We have a web app deployed on Heroku which requires ip address logging
of each request, but we noticed that the ip address is always a
10.*.*.* address (local) instead of a valid address from the
interwebs. After reading a little into this I found out that this may
be due Amazon LBS and t
