now know how to test out a
different configuration. Thank you for the help, Maxim!
~ Paul Nickerson
--
*CONFIDENTIALITY NOTICE*
The attached information is PRIVILEGED AND CONFIDENTIAL and is intended
only for the use of the addressee named above. If the reader of this
message is not the
be a strangely configured client gateway / firewall / NAT / proxy
that adds to X-Forwarded-For, but it can happen.
I guess I am still confused.
~ Paul Nickerson
--
*CONFIDENTIALITY NOTICE*
The attached information is PRIVILEGED AND CONFIDENTIAL and is intended
only for the use of th
.0.0.0/0, there is no IP that can meet this requirement.
Am I correct in my analysis?
http://nginx.org/en/docs/http/ngx_http_realip_module.html
~ Paul Nickerson
--
*CONFIDENTIALITY NOTICE*
The attached information is PRIVILEGED AND CONFIDENTIAL and is intended
only for the use of the address
ng to determine this. But I was surprised to
find there was no documentation or past forum posts saying whether this
variable came from the TCP/IP or the HTTP headers. After that, my sense of
technical discovery took over and kept me interested in the problem.
~ Paul Nickerson
--
*CONFIDENTIALITY NOTIC
ux system call.
It is the address of the peer socket.
I am going to read through socket(2) and the respective protocol man pages,
but at this point we're outside of NGINX, and so the scope of this mailing
list.
Thank you again for your help.
~ Paul Nickerson
--
*CONFIDENTIALITY NOTICE*
n track where that addr_text.data value is set.
I thought it might be coming from addr_text in the code, but my experience
with C is dated and limited. I wasn't able to figure out where
addr_text.data is set.
~ Paul Nickerson
--
*CONFIDENTIALITY NOTICE*
The attached information is PRIVILEG
lient address". Currently, my best guess is that it's the source address
field in the incoming TCP/IP packet's IPv4 internet header. Is this
correct? Or, does it come from somewhere else?
Relevant documentation:
http://nginx.org/en/docs/http/ngx_http_core_module.html#variables