git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Zdenek Wagner'" <zdenek.wagner@gmail.com>, <git@vger.kernel.org>
Subject: RE: git push does not work over https WebDAV
Date: Fri, 16 Aug 2024 22:25:17 -0400	[thread overview]
Message-ID: <011301daf04c$b6b30fe0$24192fa0$@nexbridge.com> (raw)
In-Reply-To: <CAC1phya475QkpfLp84sb=2UQs+mFos3OhuHDjmBzboeDBbtjtg@mail.gmail.com>

On Friday, August 16, 2024 9:11 PM, Zdenek Wagner wrote:
>To: git@vger.kernel.org
>What did you do before the bug happened? (Steps to reproduce your issue) git
>commit git push
>
>What did you expect to happen? (Expected behavior) The changes being pushed to
>the repo via https WebDAV
>
>What happened instead? (Actual behavior) $ git push
>error: Cannot access URL
>https://userfiles.math-gnostics.eu/git/mg-software.git/, return code
>22
>fatal: git-http-push failed
>error: failed to push some refs to
>'https://userfiles.math-gnostics.eu/git/mg-software.git'
>
>The credentials are in ~/.netrc, git clone and git pull works fine on all my repos on
>the same server, git push returns the same error
>
>Apache error log reports successfull access with the GET method (clone, pull) but
>"user not found" for the PROPFIND method
>
>What's different between what you expected and what actually happened?
>git push does not work at all
>
>Anything else you want to add:
>It is apparently an issue of git which is not OS specific, I have the same behaviour in
>Fedora 39 and Mac OSX, both having git 2.46.0. Everything works fine with git
>2.44.0 and earlier. I have
>temporarily solved my problem by downgrading git in Fedora 39. I have not trid
>2.45.0.
>
>Please review the rest of the bug report below.
>You can delete any lines you don't wish to share.
>
>
>[System Info]
>git version:
>git version 2.46.0
>cpu: x86_64
>no commit associated with this build
>sizeof-long: 8
>sizeof-size_t: 8
>shell-path: /bin/sh
>feature: fsmonitor--daemon
>libcurl: 8.9.1
>zlib: 1.3.1
>uname: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Mon Jun 24 00:56:10 PDT
>2024; root:xnu-8020.240.18.709.2~1/RELEASE_X86_64 x86_64 compiler info:
>clang: 14.0.0 (clang-1400.0.29.202) libc info: no libc information available $SHELL
>(typically, interactive shell): /bin/bash
>
>Linux penguin.czw57 6.10.3-100.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon
>Aug  5 14:46:47 UTC 2024 x86_64 GNU/Linux
>
>
>[Enabled Hooks]

Does your .curlrc specify --netrc or -n? Those appear to be required to specify the
Use of .netrc in curl.

--Randall


  reply	other threads:[~2024-08-17  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  1:11 git push does not work over https WebDAV Zdenek Wagner
2024-08-17  2:25 ` rsbecker [this message]
2024-08-17  8:14   ` Zdenek Wagner
2024-08-17  8:33     ` Zdenek Wagner
2024-08-17 15:18       ` Zdenek Wagner
2024-11-22 23:31         ` Zdenek Wagner

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='011301daf04c$b6b30fe0$24192fa0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=zdenek.wagner@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).