From: Wladimir <laanwj@gmail.com>
To: Sam Michaels <sam@samtheham.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] External IP Address
Date: Sun, 16 Mar 2014 11:22:25 +0100 [thread overview]
Message-ID: <CA+s+GJAiJTiuO-FC5cLSBi9qBAnd+HoZDdkNrJH3hGAO8hCsPQ@mail.gmail.com> (raw)
In-Reply-To: <CAHLiGBPJbpeX887irHYWgWquRv8QTBBR7s4gNZ8KE9y3ZAwJnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
Sam,
On Sun, Mar 16, 2014 at 8:04 AM, Sam Michaels <sam@samtheham.org> wrote:
> You can look for X-Client-Update to see if the check in was logged. Other
> information can be passed in the header, too.
>
> Errors are trapped so that it will always display the IP address and any
> error information is contained in the headers.
>
> Hope you find this useful.
>
Thanks for your effort.
However the current idea is to phase out reliance on centralized external
services completely in favor of peer-based address detection.
See https://github.com/bitcoin/bitcoin/pull/3461
Wladimir
[-- Attachment #2: Type: text/html, Size: 1240 bytes --]
prev parent reply other threads:[~2014-03-16 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 7:04 [Bitcoin-development] External IP Address Sam Michaels
2014-03-16 10:22 ` Wladimir [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+s+GJAiJTiuO-FC5cLSBi9qBAnd+HoZDdkNrJH3hGAO8hCsPQ@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=sam@samtheham.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox