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

git push does not work properly on git over http server

From
Jjavier.martinc@alumnos.unican.es <javier.martinc@alumnos.unican.es>
Date
Feb 10, 2009, 09:19 UTC
Message-ID
<20090210101951.2v9ltl1rqqskoc44@correo.alumnos.unican.es>

Hi, we have set up a git server over http in our office following this documentation: http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt

I have made git clone locally in another PC: git clone http://git.vsilicon.net/linux-2.6.22.y.git/

And have started developing and creating a new branch with several commits:
git checkout -b visstrim v2.6.22
Then I would like to push my new branch to the remote server:
git push --all origin
Fetching remote heads...
  refs/
  refs/tags/
  refs/heads/
'refs/heads/visstrim': up-to-date
'refs/heads/master': up-to-date
But then I do:
git branch -r
  origin/HEAD
  origin/master
And new branch hasn't gone remote.

I have tested curl succesfully and dav with cadaver and everything goes fine, I can read/write/lock without problems.

If I check apache log in LEO I can find that command "git push --all origin" only does GET http commands:

192.168.1.40 - - [10/Feb/2009:10:14:34 +0100] "PROPFIND /linux-2.6.22.y.git/ HTTP/1.1" 207 563 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:35 +0100] "HEAD /linux-2.6.22.y.git/info/refs HTTP/1.1" 200 - "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:35 +0100] "HEAD /linux-2.6.22.y.git/objects/info/packs HTTP/1.1" 200 - "-" "git/1.5.4.3" 192.168.1.40 - javier [10/Feb/2009:10:14:35 +0100] "MKCOL /linux-2.6.22.y.git/info HTTP/1.1" 301 337 "-" "git/1.5.4.3" 192.168.1.40 - javier [10/Feb/2009:10:14:35 +0100] "MKCOL /linux-2.6.22.y.git/info/ HTTP/1.1" 405 328 "-" "git/1.5.4.3" 192.168.1.40 - javier [10/Feb/2009:10:14:35 +0100] "LOCK /linux-2.6.22.y.git/info/refs HTTP/1.1" 200 481 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:35 +0100] "GET /linux-2.6.22.y.git/objects/info/packs HTTP/1.1" 200 54 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:35 +0100] "HEAD /linux-2.6.22.y.git/objects/pack/pack-344b10aeb57893911de8879e3e279847726e3151.pack HTTP/1.1" 200 - "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:35 +0100] "PROPFIND /linux-2.6.22.y.git/refs/ HTTP/1.1" 207 2599 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:36 +0100] "PROPFIND /linux-2.6.22.y.git/refs/tags/ HTTP/1.1" 207 85930 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:36 +0100] "GET /linux-2.6.22.y.git//refs/tags/v2.6.22.18 HTTP/1.1" 200 41 "-" "git/1.5.4.3" .............................................................................................................................. 192.168.1.40 - - [10/Feb/2009:10:14:46 +0100] "GET /linux-2.6.22.y.git//refs/tags/v2.6.17 HTTP/1.1" 200 41 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:46 +0100] "PROPFIND /linux-2.6.22.y.git/refs/heads/ HTTP/1.1" 207 2600 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:47 +0100] "GET /linux-2.6.22.y.git//refs/heads/visstrim HTTP/1.1" 200 41 "-" "git/1.5.4.3" 192.168.1.40 - - [10/Feb/2009:10:14:47 +0100] "GET /linux-2.6.22.y.git//refs/heads/master HTTP/1.1" 200 41 "-" "git/1.5.4.3" 192.168.1.40 - javier [10/Feb/2009:10:14:47 +0100] "UNLOCK /linux-2.6.22.y.git/info/refs HTTP/1.1" 204 - "-" "git/1.5.4.3"

Shouldn't it show PUT commands since git push is supposed to upload data to remote server?

Any idea? I have been looking for this problem through the net for several days with no success.

Next: Johannes Schindelin
Message 1 of 2 in “git push does not work properly on git over http server”
  1. javier.martinc@alumnos.unican.esFeb 10, 2009
  2. Johannes SchindelinFeb 10, 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.