What is the proper way to configure Nginx reverse proxy headers when behind an AWS Classic Load Balancer to preserve client IP addresses?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What is the proper way to configure Nginx reverse proxy headers when behind an AWS Classic Load Balancer to preserve client IP addresses?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
AWS Classic Load Balancer X-Forwarded-For header Nginx real_ip_header set_real_ip_from documentation Google ↗
Nginx ngx_http_realip_module real_ip_header set_real_ip_from documentation proxy protocol AWS Classic Load Balancer Google ↗
- Module ngx_http_realip_module · nginx.org
- HTTP headers and Classic Load Balancers · docs.aws.amazon.com
- Configure proxy protocol for your Classic Load Balancer · docs.aws.amazon.com
- Accepting the PROXY Protocol · docs.nginx.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
AWS Classic Load Balancer X-Forwarded-For header Nginx real_ip_header set_real_ip_from documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Nginx ngx_http_realip_module real_ip_header set_real_ip_from documentation proxy protocol AWS Classic Load Balancer OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |