On Sun, Feb 21, 2016 at 03:29:56PM -0800, Junio C Hamano wrote: > This feels 70% like "how to configure your Apache server when you > run site that is contacted by a client that is slow to talk?", that > is not necessarily specific to Git. It's specific to Git in the sense that Git seemingly as a normal matter of course posts very slowly to /git-upload-pack. Normal HTTP clients don't work this way; they typically have their entire POST body ready before they decide to make a request. > Also while it may make sense to tweak the timeout on the server > side, recommending to disable it altogether, instead of adjusting to > the typical requirement for a sane client, feels just wrong. True, although I have no idea what the right limits would be. > Also, are all requests from one client slow to start, or are only > some phases in the protocol exchange slow but not others? If the > server side can tell which ones could be normally slow, selectively > loosening timeouts only for them might be more palatable, but I am > sensing that you are not suggesting such an approach. I know only of /git-upload-pack having this pattern, and it is the only one I am seeing 408 errors for in my logs. It seems to fail very rarely (~0.2% of all /git-upload-pack requests), but for some users, it's seemingly very persistent. /* Steinar */ -- Homepage: https://www.sesse.net/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html