From: willievu <willievu@dev.java.net>
To: git@vger.kernel.org
Subject: http-push sends MKCOL command to create remote directory MKCOL http://user@server:80/url/.git/refs/ that already exists
Date: Fri, 14 Aug 2009 10:42:01 -0500 (CDT) [thread overview]
Message-ID: <1250264521299-3445796.post@n2.nabble.com> (raw)
Steps will reproduce the problem:
1. create a bare & shared repository locally and copy to remote server
2. create a local repository. add and commit some files
3. git push to the remote server
$ git push --verbose --thin upload HEAD
Pushing to http://user@server/url/.git/
Password:
Fetching remote heads...
refs/
refs/heads/
refs/tags/
updating 'refs/heads/master' using 'HEAD'
from 0000000000000000000000000000000000000000
to 0120f45ebfd90501868e990bfbb9f50fb0a8ebae
<<<<< Here, a MKCOL http://user@server:80/url/.git/refs/ request is sent.
The WebDAV server returns a HTTP 500 Internal Server Error. Then, the
following message continues:
Unable to create branch path http://user@server/url/.git/refs/
Unable to lock remote branch refs/heads/master
error: failed to push some refs to 'http://user@server/url/.git/'
This is the server:
Server: Oracle9iAS/9.0.2.3.0 Oracle HTTP Server (Unix) mod_plsql/9.0.2.6.0b
DAV/1.0.3.2.4-0119 (OraDAV enabled) mod_osso/9.0.2.0.0 mod_ossl/9.0.2.0.0
mod_fastcgi/2.2.12 mod_perl/1.26 mod_oc4j/3.0
Is MKCOL expected even for existing directory in the remote repository? Is
this a WebDAV server problem that 500 is returned?
--
View this message in context: http://n2.nabble.com/http-push-sends-MKCOL-command-to-create-remote-directory-MKCOL-http%3A--user%40server%3A80-url-.git-refs--that-already-exists-tp3445796p3445796.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2009-08-14 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 15:42 willievu [this message]
2009-08-15 1:28 ` http-push sends MKCOL command to create remote directory MKCOL http://user@server:80/url/.git/refs/ that already exists Tay Ray Chuan
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=1250264521299-3445796.post@n2.nabble.com \
--to=willievu@dev.java.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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