git http-push

Object-by-object upload over plain HTTP. Almost never wanted.

🎯 What & why

git http-push uploads objects and updates refs over plain HTTP using WebDAV-style PUT/MOVE/DELETE. It is the writing counterpart to git http-fetch and exists only because dumb HTTP has no receive-pack.

🧠 Mental model

Imagine using curl -X PUT to copy each loose object into the remote's objects/ tree, then PUT-ing the new ref file. That is literally what this does. There is no negotiation, no atomic transaction, and no hooks fire on the server.

🛠️ Synopsis

git http-push [--all] [--dry-run] [--force] [--verbose]
              [-D] [-d] <url> <ref> [<ref>...]

Requires a WebDAV-enabled HTTP server. Writes objects under `objects/` and rewrites ref files under `refs/`. No server-side validation.

🎚️ Switches & options

Flag	What it does
`<url> <refs>`	Remote base URL and one or more refs to push (e.g. `refs/heads/main`).
`-D`	⚠️ Delete the named refs on the remote (with `-d`, expects `ref:dst` form).
`-d`	Same as `-D` but using the `<src>:<dst>` refspec form.
`-f, --force`	⚠️ Allow non-fast-forward updates -- overwrites history on the remote.
`--all`	Push all refs under `refs/heads/`.
`-v, --verbose`	Print each object/ref operation as it happens.
`--dry-run`	Show what would be sent without uploading anything.

💡 Use cases

Legacy WebDAV-backed Git mirrors that predate git http-backend.
One-off recovery push to a static-file host you happen to have PUT access to.
Pedagogical demonstration of why the smart protocol exists.
Almost nothing else -- prefer ssh or smart HTTPS in every modern setup.

🧪 Examples

Push main over WebDAV

git http-push http://127.0.0.1/repo.git/ refs/heads/main

Force-push everything (DANGER)

git http-push --force --all http://127.0.0.1/repo.git/

Delete a remote branch

git http-push -D http://127.0.0.1/repo.git/ refs/heads/old-topic

Preview without uploading

git http-push --dry-run -v http://127.0.0.1/repo.git/ refs/heads/main

🎓 Recommendations

Do not use this. Run git http-backend (smart HTTP) or push via ssh.
If you truly cannot avoid it, mirror immediately via smart protocol so future pushes are sane.
Always --dry-run -v first -- there are no server hooks to catch a bad push.

🪤 Common pitfalls

No pre-receive/update/post-receive hooks fire -- bad data lands without review.
The push is not atomic; an interrupted upload can leave the remote with dangling objects and an unmoved ref.
WebDAV PUT requires the server to allow writes to objects/ and refs/ -- a security footgun if misconfigured.

🔗 Related modules

📝 Quiz

Hit each option, then Check answers. Score is recorded; Next is always open.