git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git dumb HTTP protocol should use WebDAV PROPFIND method

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 8, 2025, 18:47 UTC
Message-ID
<xmqqikhswzl7.fsf@gitster.g>
In-Reply-To
<CAGiEHCv7kXSB5v8Pi6gDYaC2O3m5qEM8dYW3vKvNm6sXQ_Vuhw@mail.gmail.com>
Milan Hauth <milahu@gmail.com> writes:
Show 7 quoted lines
> 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.

Previous: Milan HauthNext: Milan Hauth
Message 2 of 3 in “Git dumb HTTP protocol should use WebDAV PROPFIND method”
  1. Milan HauthSep 8, 2025
  2. Junio C HamanoSep 8, 2025
  3. Milan HauthSep 8, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.