All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alecs King <alecsk@gmail.com>
Cc: git@vger.kernel.org,  Arti Zirk <arti.zirk@gmail.com>
Subject: Re: [PATCH] instaweb: fix ip binding for the python http.server
Date: Fri, 10 Jan 2025 15:32:51 -0800	[thread overview]
Message-ID: <xmqq5xmm5joc.fsf@gitster.g> (raw)
In-Reply-To: <20250110101346.30416-1-alecsk@gmail.com> (Alecs King's message of "Fri, 10 Jan 2025 18:13:46 +0800")

Alecs King <alecsk@gmail.com> writes:

> `git instaweb -d python` should bind the server to 0.0.0.0
> `git instaweb -d python -l` should bind the server to 127.0.0.1

That is a correct statement of the fact.  What makes this patch
worthwhile is that the current code gets it the other way around
since its inception at 2eb14bb2 (git-instaweb: add Python builtin
http.server support, 2019-01-28).

Well spotted.

There seem to be some backends that simply ignore the "--local"
option.  Should they be somehow "fixed" (or at least making it a
documented bug)?  It is not within the scope of this patch, but
since the script has our attention...

Thanks, will queue.

>
> Signed-off-by: Alecs King <alecsk@gmail.com>
> ---
>  git-instaweb.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/git-instaweb.sh b/git-instaweb.sh
> index 5ad50160bb..7b44f70789 100755
> --- a/git-instaweb.sh
> +++ b/git-instaweb.sh
> @@ -694,9 +694,9 @@ class GitWebRequestHandler(CGIHTTPRequestHandler):
>  		return result
>  
>  
> -bind = "127.0.0.1"
> +bind = "0.0.0.0"
>  if "$local" == "true":
> -	bind = "0.0.0.0"
> +	bind = "127.0.0.1"
>  
>  # Set our http root directory
>  # This is a work around for a missing directory argument in older Python versions

  reply	other threads:[~2025-01-10 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 10:13 [PATCH] instaweb: fix ip binding for the python http.server Alecs King
2025-01-10 23:32 ` Junio C Hamano [this message]
2025-01-15  9:24 ` Arti Zirk

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=xmqq5xmm5joc.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=alecsk@gmail.com \
    --cc=arti.zirk@gmail.com \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.