News for hackers. Stuff that matters.

A comment on Chrome Data Compression Proxy for Carriers and ISPs.

Re:Chrome Data Compression Proxy for Carriers and ISPs by caleblloyd on Sunday April 03, 2016 @10:35AM (#11416230)
"Because requests to destination websites are sent from Google's servers, the IP address of the client making the connection will reflect the location of Google's servers, not the user. The DCP sends the IP address of the client in the X-Forwarded-For header with each request, for example: X-Forwarded-For: 74.125.239.111"

Web servers shouldn't blindly respect this X-Forwarded-For header coming from any random server.

[ Parent | on HN ]
Re:Chrome Data Compression Proxy for Carriers and ISPs by dantiberian on Sunday April 03, 2016 @01:45PM (#11416891)
Websites should use the X-Forwarded-For header to determine the IP address of the client for the purpose of IP geolocation.

I don't think they're suggesting you just assume that the IP is correct, only that if you are doing some kind of regional customisation that you can use that X-Forwarded-For header to help.

[ Parent | on HN ]