cherokee at googlecode
Sep 22, 2010, 5:36 AM
Views: 532
Permalink
|
|
Issue 997 in cherokee: RFE: X-Forwarded-For header as REMOTE_ADDR with FastCGI
|
|
Status: New
Owner: ----
New issue 997 by r...@ayumi.de: RFE: X-Forwarded-For header as REMOTE_ADDR
with FastCGI
http://code.google.com/p/cherokee/issues/detail?id=997
What steps will reproduce the problem?
1. Set up a vhost with fcgi handler (e.g. PHP wizard)
2. Set up logging so it logs the X-Real-IP (XRI) header as client IP
3. Set up the fcgi handler so it sets the X-Real-IP (XRI) header as
REMOTE_ADDR
4. Make requests with X-Forwarded-For (XFF) header
What is the expected output? What do you see instead?
Seen:
logged client IP = XFF header
REMOTE_ADDR = proxy IP
Expected:
logged client IP = XFF header
REMOTE_ADDR = XFF header
What version of the product are you using? On what operating system?
1.0.8 Debian squeeze/testing
Please provide any additional information below.
It is possible to set the logging so it uses the XRI header. This also
values the XFF header.
The FastCGI handler also allows using the XRI header as REMOTE_ADDR.
However, opposing to the logging behavior, it does NOT respect the XFF
header.
That is not actually a bug, since the admin mentions the XFF header only
for the logging part. But it's well worth being irritated about it.
The fix seems easy (see attached patch), but I didn't have time to test it
yet.
Attachments:
cherokee_fcgi_xff.patch 671 bytes
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
Issue 997 in cherokee: RFE: X-Forwarded-For header as REMOTE_ADDR with FastCGI
