Opened 11 years ago
Closed 10 years ago
#531 closed enhancement (fixed)
source port logging
Reported by: | ghen.myopenid.com | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | nginx-core | Version: | 1.4.x |
Keywords: | mail client source port logging | Cc: | |
uname -a: | Linux hostname 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | ||
nginx -V: | nginx version: nginx/1.4.7 |
Description
Due to the increasing use of Carrier-Grade NAT (CGN) at Internet Service Providers, new EU legislation will soon require service providers to log source ports in addition to source IP's to allow identifying individual end users (as a single IP may have multiple independent users behind it).
For HTTP (access_log) this can be done in configuration using $server_port.
For pop3/imap the log format (error_log) is hardcoded, so it must be changed in the code to include the source port of pop3/imap requests. Can this be considered?
Attachments (1)
Change History (6)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Some of this does still apply directly to the mainline nginx code base, so should be updated.
by , 10 years ago
Attachment: | hg-http.patch added |
---|
This patch adds the source port to all http(s) error output
comment:3 by , 10 years ago
Linking the mailing list thread here:
http://mailman.nginx.org/pipermail/nginx-devel/2014-April/005249.html
comment:5 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
With d5b8ee9f2201, the client port is output in the "connected to" log messages.
This ticket appears to be based on the Zimbra version of nginx, so it is not particularly applicable.