←back to thread

A New Future for Icanhazip

(major.io)
980 points nkcmr | 1 comments | 06 Jun 21 19:21 UTC | HN request time: 0s | source
Show context
ColdHeat ◴[06 Jun 21 20:06 UTC] No.27415866[source]▶
I used to use this site until I found https://checkip.amazonaws.com/. Switched because I wasn't sure who was behind icanhazip.com and it's tough to beat AWS. Glad to hear that it will likely be maintained for awhile longer!
replies(2): >>27415952 #>>27416424 #
madars ◴[06 Jun 21 20:18 UTC] No.27415952[source]▶
Something to be aware of: checkip.amazonaws.com will happily return an X-Forwarded-For address https://stackoverflow.com/questions/52618096/under-what-circ...
replies(1): >>27416056 #
kortilla ◴[06 Jun 21 20:32 UTC] No.27416056[source]▶
Use https
replies(1): >>27416225 #
lucb1e ◴[06 Jun 21 20:52 UTC] No.27416225{3}[source]▶
That has nothing to do with an HTTP header. See for yourself:

    $ curl -HX-Forwarded-For:127.0.0.1 https://checkip.amazonaws.com
    127.0.0.1
replies(3): >>27416246 #>>27416267 #>>27481936 #
1. gruez ◴[06 Jun 21 20:56 UTC] No.27416246{4}[source]▶
I think the point is to prevent middleboxes (eg. caching proxy servers) from interfering with the request. Otherwise I don't really see the issue with the ip address being affected by X-Forwarded-For. You can just... not specify the header.