[TYPO3-core] RFC: Fix bug #7397: Proxy servers replace REMOTE_ADDR with their own IP

[Michael Stucki]

This is a SVN patch request.

Problem:
When requesting the clients REMOTE_ADDR, it can happen that there is a proxy
in between server and client, which replaces the value with his own IP, and
puts the original IP in HTTP_X_FORWARDED_FOR instead.

Solution:
Add a new configuration option to send HTTP_X_FORWARDED_FOR when requesting
the REMOTE_ADDR.

Branches:
Trunk only

Bugtracker reference:
http://bugs.typo3.org/view.php?id=7397
http://bugs.typo3.org/view.php?id=169 (should also be fixed by this change)

Comments:
I am not sure how to deal with the REMOTE_HOST field. I suppose it must be
wrong, too, but there seems no replacement for it.
Currently, I also send HTTP_X_FORWARDED_FOR when asking for REMOTE_HOST,
however there could be conflicts when a hostname is requested, and an IP is
returned(?)

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug_7397.diff
Type: text/x-diff
Size: 2650 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20080205/35efa9fc/attachment.diff