Global HTTP timeouts vs per-request context cancellation for long Git operations in Forgejo
I'm running a Forgejo instance (v1.21-era configuration) that regularly serves large repository pushes and LFS transfers, and I need to decide how to protect the server without breaking legitimate long-running operations. From the documentation, the [server] section in app.ini exposes ReadTimeout , ReadHeaderTimeout , and WriteTimeout , enforced globally by
git