On 27 March 2010 04:28, Deron Meranda <[email protected]> wrote: > However, blocked-flushing of dynamic output like this is really the what > chunked transfer encoding and the HTTP 100 Continue responses are > for ... as a means of streaming and explicit blocking. > > I'm not sure how well mod_wsgi supports that though.
Underlying Apache handles it, not mod_wsgi. That said, mod_wsgi does have a slight fiddle related to it to workaround a bug in 100-continue processing in Apache <2.2.8 and force the correct behaviour. Anyway, you don't need to do anything. If no content length and HTTP client is 1.1 then Apache will use chunked encoding on responses. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
