U:RDoc::AnyMethod[iI"new:ETI""ActionDispatch::RemoteIp::new;TT:publico:RDoc::Markup::Document:@parts[
o:RDoc::Markup::Paragraph;	[I"1Create a new +RemoteIp+ middleware instance.;To:RDoc::Markup::BlankLineo;
;	[
I"LThe +ip_spoofing_check+ option is on by default. When on, an exception ;TI"Mis raised if it looks like the client is trying to lie about its own IP ;TI"Maddress. It makes sense to turn off this check on sites aimed at non-IP ;TI"Jclients (like WAP devices), or behind proxies that set headers in an ;TI"/incorrect or confusing way (like AWS ELB).;T@o;
;	[
I"KThe +custom_proxies+ argument can take an Array of string, IPAddr, or ;TI"JRegexp objects which will be used instead of +TRUSTED_PROXIES+. If a ;TI"Msingle string, IPAddr, or Regexp object is provided, it will be used in ;TI"Kaddition to +TRUSTED_PROXIES+. Any proxy setup will put the value you ;TI"Kwant in the middle (or at the beginning) of the X-Forwarded-For list, ;TI"Lwith your proxy servers after it. If your proxies aren't removed, pass ;TI"Othem in via the +custom_proxies+ parameter. That way, the middleware will ;TI"Aignore those IP addresses, and return the one that you want.;T:
@fileI"0lib/action_dispatch/middleware/remote_ip.rb;T:0@omit_headings_from_table_of_contents_below000[I":(app, ip_spoofing_check = true, custom_proxies = nil);T@ FI"
RemoteIp;TcRDoc::NormalClass00