U:RDoc::AnyMethod[iI"set_remote_address:ETI"!Puma::DSL#set_remote_address;TF:publico:RDoc::Markup::Document:@parts[
o:RDoc::Markup::Paragraph;	[	I"CControl how the remote address of the connection is set. This ;TI"Gis configurable because to calculate the true socket peer address ;TI"Da kernel syscall is required which for very fast rack handlers ;TI"+slows down the handling significantly.;To:RDoc::Markup::BlankLineo;
;	[I"!There are 5 possible values:;T@o:RDoc::Markup::List:
@type:NUMBER:@items[
o:RDoc::Markup::ListItem:@label0;	[o;
;	[	I"M**:socket** (the default) - read the peername from the socket using the ;TI"Osyscall. This is the normal behavior. If this fails for any reason (e.g., ;TI"Wif the peer disconnects between the connection being accepted and the getpeername ;TI"-system call), Puma will return "0.0.0.0";To;;0;	[o;
;	[I";**:localhost** - set the remote address to "127.0.0.1";To;;0;	[o;
;	[I"K**header: <http_header>**- set the remote address to the value of the ;TI")provided http header. For instance: ;TI"/`set_remote_address header: "X-Real-IP"`. ;TI"MOnly the first word (as separated by spaces or comma) is used, allowing ;TI"Sheaders such as X-Forwarded-For to be used as well. If this header is absent, ;TI"3Puma will fall back to the behavior of :socket;To;;0;	[o;
;	[I"P**proxy_protocol: :v1**- set the remote address to the value read from the ;TI"OHAproxy PROXY protocol, version 1. If the request does not have the PROXY ;TI"7protocol attached to it, will fall back to :socket;To;;0;	[o;
;	[I"R**\<Any string\>** - this allows you to hardcode remote address to any value ;TI"Iyou wish. Because Puma never uses this field anyway, it's format is ;TI"entirely in your hands.;T:
@fileI"lib/puma/dsl.rb;T:0@omit_headings_from_table_of_contents_below000[I"(val=:socket);T@<FI"DSL;TcRDoc::NormalClass00