Hello Roberto, On 29/04/2010, at 03:09, Roberto De Ioris wrote: > Il giorno mer, 28/04/2010 alle 23.18 +0200, Alvaro Lopez Ortega ha > scritto: > >> Cherokee does not buffer posts any longer, instead, it retransmits it to the >> backend as it's received from the client. >> >> Could you please try the same test with another backend (SCGI, FastCGI or >> HTTP with the reverse proxy)? Let's try to narrow possible causes of the >> problem. > > Hi Alvaro, the Patrick problem is that he has to use the harakiri mode > of uWSGI but on "streamed" uploads the timer starts at connection > opening so if the client does not send data fastly the harakiri will > kill the request. > > So this is a "logic" problem, more than an issue. > If Cherokee cannot be re-put in "buffering-mode" i think that the only > solution would be do buffering on uWSGI (save the uploaded data on a > temporary file before starting the harakiri-timer).
Alright, now I get it. Cherokee will re-implement the POST buffering mechanism eventually, although it isn't a high-priority task right now. In most of the cases the 'live-replay' is more useful than the 'buffered' mechanism (scripts execution is triggered sooner, the post status report module is available, and so on). So, is there a way/workaround to get this working with uWSGI until we re-implement the buffered-post support? Cheers! -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
