unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK
Date: Thu, 03 Feb 2022 08:25:05 +0100	[thread overview]
Message-ID: <87o83o2yv8.fsf@web.de> (raw)
In-Reply-To: <20220203002638.34504-1-aconchillo@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]


Aleix Conchillo Flaqué <aconchillo@gmail.com> writes:

> Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when
> starting the web server inside containers without the need to having to
> specify INADDR_ANY all the time. This is the default in most libraries
> and languages.
>
> This doesn't break backwards compatibility since INADDR_LOOPBACK is also
> included in INADDR_ANY.

I’d like to know whether there was a specific reason not to use it.

I prefer the new behavior (ANY), because it’s less surprising (it once
surprised me that it was different).

It might be an option to switch to IPV6 ANY instead to get a real ANY.
But there are different opinions about this.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2022-02-03  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  0:26 [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK Aleix Conchillo Flaqué
2022-02-03  7:25 ` Dr. Arne Babenhauserheide [this message]
2022-07-22  0:44 ` Aleix Conchillo Flaqué
2022-07-22  9:44   ` Maxime Devos
2022-07-22 17:14     ` Aleix Conchillo Flaqué
2022-07-22 11:45   ` Greg Troxel
2022-07-22 17:16     ` Aleix Conchillo Flaqué

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o83o2yv8.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=aconchillo@gmail.com \
    --cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).