From: Junio C Hamano <gitster@pobox•com>
To: Milan Hauth <milahu@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Git dumb HTTP protocol should use WebDAV PROPFIND method
Date: Mon, 08 Sep 2025 11:47:48 -0700 [thread overview]
Message-ID: <xmqqikhswzl7.fsf@gitster.g> (raw)
In-Reply-To: <CAGiEHCv7kXSB5v8Pi6gDYaC2O3m5qEM8dYW3vKvNm6sXQ_Vuhw@mail.gmail.com> (Milan Hauth's message of "Mon, 8 Sep 2025 14:10:34 +0200")
Milan Hauth <milahu@gmail•com> writes:
> workaround:
>
> pushd /path/to/repo/.git/
> git --bare update-server-info
> mv hooks/post-update.sample hooks/post-update
> popd
> git ls-remote http://localhost/src/somerepo/.git/
That is not a workaround, but the proper way the system was designed
to be used.
After all, the "dumb HTTP" support is just that. It is known to be
ultra inefficient relative to other transport methods like "git
protocol over ssh connection", and "smart HTTP stateless
connection", and the WHOLE point of supporting "dumb HTTP" transport
is to allow a truly dumb HTTP serving infrastructure. Letting the
clients assume that WebDAV exists on the server side defeats its
reason to exist.
next prev parent reply other threads:[~2025-09-08 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 12:10 Git dumb HTTP protocol should use WebDAV PROPFIND method Milan Hauth
2025-09-08 18:47 ` Junio C Hamano [this message]
2025-09-08 19:09 ` Milan Hauth
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=xmqqikhswzl7.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=milahu@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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