Project

General

Profile

Actions

Feature #1718

closed

working with Nginx x-real-ip, Can not get the real Client IP

Added by suchasplus over 16 years ago. Updated about 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
mod_accesslog
Target version:
ASK QUESTIONS IN Forums:

Description

I used Nginx as Proxy at the front running 80 port, Lighttpd running 10080 port, Apache @ 10081 port. Lighttpd and Apache both have combined mode log.
I need the client IP to analyze some information.
I access the domain @lighttpd via Nginx@80port, Lighttpd's access_log can not get the client's real IP like 124.130.125.196, Lighttpd logged as 127.0.0.1, When I access the domain @lighttpd via 10080 port(direct to lighttpd), it can log correctly as 124.130.125.196.
Apache always can get the real client IP.

Actions #1

Updated by suchasplus over 16 years ago

Replying to suchasplus:

I used Nginx as Proxy at the front running 80 port, Lighttpd running 10080 port, Apache @ 10081 port. Lighttpd and Apache both have combined mode log.
I need the client IP to analyze some information.
I access the domain @lighttpd via Nginx@80port, Lighttpd's access_log can not get the client's real IP like 124.130.125.196, Lighttpd logged as 127.0.0.1, When I access the domain @lighttpd via 10080 port(direct to lighttpd), it can log correctly as 124.130.125.196.
Apache always can get the real client IP.

Sorry, '''It's a mistake'''
mod_extforward is useful

Actions #2

Updated by stbuehler about 16 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid
Actions #3

Updated by stbuehler about 16 years ago

for x-real-ip see #1545

Actions #4

Updated by stbuehler about 16 years ago

  • Status changed from Fixed to Invalid
Actions

Also available in: Atom