Class: LogjamAgent::ActionDispatch::RemoteIp::GetIp
- Inherits:
-
Object
- Object
- LogjamAgent::ActionDispatch::RemoteIp::GetIp
- Defined in:
- lib/logjam_agent/actionpack/lib/action_dispatch/middleware/remote_ip.rb
Overview
The GetIp class exists as a way to defer processing of the request data into an actual IP address. If the ActionDispatch::Request#remote_ip method is called, this class will calculate the value and then memoize it.
Instance Method Summary collapse
-
#calculate_ip ⇒ Object
Sort through the various IP address headers, looking for the IP most likely to be the address of the actual remote client making this request.
-
#initialize(env, middleware) ⇒ GetIp
constructor
A new instance of GetIp.
-
#to_s ⇒ Object
Memoizes the value returned by #calculate_ip and returns it for ActionDispatch::Request to use.
Constructor Details
#initialize(env, middleware) ⇒ GetIp
Returns a new instance of GetIp.
92 93 94 95 96 |
# File 'lib/logjam_agent/actionpack/lib/action_dispatch/middleware/remote_ip.rb', line 92 def initialize(env, middleware) @env = env @check_ip = middleware.check_ip @proxies = middleware.proxies end |
Instance Method Details
#calculate_ip ⇒ Object
Sort through the various IP address headers, looking for the IP most likely to be the address of the actual remote client making this request.
REMOTE_ADDR will be correct if the request is made directly against the Ruby process, on e.g. Heroku. When the request is proxied by another server like HAProxy or NGINX, the IP address that made the original request will be put in an X-Forwarded-For header. If there are multiple proxies, that header may contain a list of IPs. Other proxy services set the Client-Ip header instead, so we check that too.
As discussed in this post about Rails IP Spoofing, while the first IP in the list is likely to be the “originating” IP, it could also have been set by the client maliciously.
In order to find the first address that is (probably) accurate, we take the list of IPs, remove known and trusted proxies, and then take the last address left, which was presumably set by one of those proxies.
116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 |
# File 'lib/logjam_agent/actionpack/lib/action_dispatch/middleware/remote_ip.rb', line 116 def calculate_ip # Set by the Rack web server, this is a single value. remote_addr = ips_from('REMOTE_ADDR').last # Could be a CSV list and/or repeated headers that were concatenated. client_ips = ips_from('HTTP_CLIENT_IP').reverse forwarded_ips = ips_from('HTTP_X_FORWARDED_FOR').reverse # +Client-Ip+ and +X-Forwarded-For+ should not, generally, both be set. # If they are both set, it means that this request passed through two # proxies with incompatible IP header conventions, and there is no way # for us to determine which header is the right one after the fact. # Since we have no idea, we give up and explode. should_check_ip = @check_ip && client_ips.last && forwarded_ips.last if should_check_ip && !forwarded_ips.include?(client_ips.last) # We don't know which came from the proxy, and which from the user raise IpSpoofAttackError, "IP spoofing attack?! " + "HTTP_CLIENT_IP=#{@env['HTTP_CLIENT_IP'].inspect} " + "HTTP_X_FORWARDED_FOR=#{@env['HTTP_X_FORWARDED_FOR'].inspect}" end # We assume these things about the IP headers: # # - X-Forwarded-For will be a list of IPs, one per proxy, or blank # - Client-Ip is propagated from the outermost proxy, or is blank # - REMOTE_ADDR will be the IP that made the request to Rack ips = [forwarded_ips, client_ips, remote_addr].flatten.compact # If every single IP option is in the trusted list, just return REMOTE_ADDR filter_proxies(ips).first || remote_addr end |
#to_s ⇒ Object
Memoizes the value returned by #calculate_ip and returns it for ActionDispatch::Request to use.
150 151 152 |
# File 'lib/logjam_agent/actionpack/lib/action_dispatch/middleware/remote_ip.rb', line 150 def to_s @ip ||= calculate_ip end |