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

Re: Does smart-http need git-daemon-export-ok?

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 26, 2009, 17:33 UTC
Message-ID
<7vk4w963np.fsf@alter.siamese.dyndns.org>
In-Reply-To
<905315640912260821k2fb149b3je69dbea5463afaa3@mail.gmail.com>
Tarmigan <tarmigan+git@gmail.com> writes:
> Should the git-http-backend check something like git-daemon-export-ok
> before serving a repository?

I'd agree that it would make sense to have a way to mark individual repository for (or not for) export.

In "native" case, the chain of events are: client talks to the daemon, the daemon checks and decides to (or not to) export, and it runs upload-pack.

In "smart http" case, http-backend is one half of what corresponds to the daemon (the other half being your http server configuration), and it is more flexible and git specific half, so I'd say it would make sense to implement the check that honors the same git-daemon-export-ok flag file in it.

Previous: TarmiganNext: Tarmigan Casebolt
Message 2 of 14 in “Does smart-http need git-daemon-export-ok?”
  1. TarmiganDec 26, 2009
  2. Junio C HamanoDec 26, 2009
  3. 1/2 Smart-http: Add tests and documentation for export-okTarmigan Casebolt, Dec 26, 2009
  4. 2/2 Smart-http: check if repository is OK to export before serving itTarmigan Casebolt, Dec 26, 2009
  5. Shawn O. PearceDec 27, 2009
  6. TarmiganDec 28, 2009
  7. Smart-http: check if repository is OK to export before serving itTarmigan Casebolt, Dec 28, 2009
  8. Shawn O. PearceDec 28, 2009
  9. TarmiganDec 28, 2009
  10. Shawn O. PearceDec 28, 2009
  11. Smart-http: check if repository is OK to export before serving itTarmigan Casebolt, Dec 28, 2009
  12. Junio C HamanoDec 29, 2009
  13. Shawn O. PearceDec 29, 2009
  14. Shawn O. PearceDec 27, 2009

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.