DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30195>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30195 add proxy backend src port to r->notes for logging Summary: add proxy backend src port to r->notes for logging Product: Apache httpd-2.0 Version: 2.0-HEAD Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] There are no hooks in mod_proxy to discover from what src port mod_proxy is initiating a proxy connection. This information can be useful for logging purposes. I've implemented a patch for both apache-1.3.31 and apache-2.0 HEAD that accomplishes this. Here's another example of how this could be useful: I want to allow CONNECT requests to localhost on port 5000, for proxying protocol P over port 80. Application 'MyAPP' listens on port 5000 for protocol P. I want MyAPP to know the real source IP/Port that the connection came in on, but MyAPP and mod_proxy don't know about each other at all. The only pseudo-unique shared key between them is the source port used by mod_proxy to initiate the connection. If I could run a PerlCleanupHandler that will take the "proxy_source_port" from r->notes and store it in a database along with the client_source_port and client_source_ip, then MyAPP could read this from the database and retrieve the client_source_port and client_source_ip. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
