> On Tue, May 10, 2016 at 10:44:27AM +0200, Roberto De Ioris wrote: >> > I'm trying to set up uwsgi with cgi plugin and git-http-backend, to >> > see if we get better performance with uwsgi over fastcgi (http-git >> > performance is fairly important to us for git.kernel.org). >> > >> > However, all my attempts have been in vain thus far, because >> attempting >> > to clone always hangs -- GETs work just fine, but when we try to do a >> > POST, git-http-backend enters endless read() and then things time out. >> > Apparently, this is because STDIN with POST data is never closed. >> Hi again, this patch should address it: >> >> https://github.com/unbit/uwsgi/commit/ac1e354fcf16583a5b242bb0ed36fa5e3be41701 >> (just add cgi-close-stdin-on-eof = true to the options) > > Thanks, Roberto, I'll check it out. Shouldn't this be true by default, > since otherwise CGI POST doesn't work at all? >
Hi, our first rule is "never change behaviours before a looong deprecation phase". uWSGI cgi plugin is one of the most used one, so it is a risk to change an established behaviours (stdin like in a WSGI/PSGI/Rack app). In 2.1 we can absolutely think about setting it as the default -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
