Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am developing a web service that another group is developing a web front end against. My web service needs to do some IP Address logging of the web client, so I need the web front end to pass me the IP Address of the actual user in a HTTP header. My original thought was to use X-Forwarded-For, but that did not feel completely correct, is there a better header for this?
Note: The REST client is trusted and authenticated, so I am not worry about a malicious client spoofing the source address.
I think
X-Forwarded-Forsounds like the perfect header for your use-case. It’s supported by many proxy servers and although it’s not ratified in an RFC, the problem it solves is so small that there’s little chance of interoperability problems. Why don’t you want to use it?