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

http-smart-backend: can clone, cannot push

From
Jeremiah Foster <jeremiah.foster@pelagicore.com>
Date
Jun 1, 2010, 12:28 UTC
Message-ID
<E66CC81A-CCED-4D8E-AE7C-C02FB0AF6F6C@pelagicore.com>
Hello,
	I've set up a directory to serve git repos under /var/www/git using:
	- apache2
	- git 1.7.1
	
	The apache config file is literally pasted from the http-smart-backend documentation, modified for my installation. I clone successfully over https using the smart backend. I know this because when you use the smart backend you get this type of message:
	git clone https://git.pelagicore.net/var/www/git/administrivia.git
	Initialized empty Git repository in /home/jeremiah/administrivia/.git/
	remote: Counting objects: 69, done.
	remote: Compressing objects: 100% (47/47), done.
	remote: Total 69 (delta 15), reused 0 (delta 0)
	Unpacking objects: 100% (69/69), done.
	As opposed to a more terse message when using a 'dumb' http transport.
	I cannot push however. This is what git says:
	
	$ ~/administrivia >  git push origin master
	error: Cannot access URL https://git.pelagicore.net/var/www/git/administrivia.git/, return code 22
	fatal: git-http-push failed
	And this is what the logs say:
	[Tue Jun 01 14:25:54 2010] [error] [client 109.74.195.212] Request not supported: '/var/www/git/administrivia.git/'
	How is that I can clone with the smart transport, and not push?
Thanks,
Jeremiah
Next: Tay Ray Chuan
Message 1 of 9 in “http-smart-backend: can clone, cannot push”
  1. Jeremiah FosterJun 1, 2010
  2. Tay Ray ChuanJun 1, 2010
  3. Jeremiah FosterJun 1, 2010
  4. Tay Ray ChuanJun 1, 2010
  5. Jeremiah FosterJun 1, 2010
  6. Shawn O. PearceJun 1, 2010
  7. Antonio García DomínguezJun 1, 2010
  8. Jeremiah FosterJun 2, 2010
  9. Erik Faye-LundJun 1, 2010

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.