On 06/04/07, James Y Knight <[EMAIL PROTECTED]> wrote:
>
> On Apr 5, 2007, at 10:52 PM, Graham Dumpleton wrote:
>
> > On 06/04/07, James Y Knight <[EMAIL PROTECTED]> wrote:
> >> What's the point of a switch? If the app didn't provide a content-
> >> length, and you can't otherwise determine a conte
On Apr 5, 2007, at 10:52 PM, Graham Dumpleton wrote:
> On 06/04/07, James Y Knight <[EMAIL PROTECTED]> wrote:
>> What's the point of a switch? If the app didn't provide a content-
>> length, and you can't otherwise determine a content-length (because
>> for example the result is a simple list of
On 06/04/07, James Y Knight <[EMAIL PROTECTED]> wrote:
>
> On Apr 5, 2007, at 10:08 PM, Graham Dumpleton wrote:
> > FWIW, in mod_wsgi I have now added a directive which allows one to
> > enable within a specific context that chunked transfer encoding should
> > be used for a response when a HTTP/1.
On Apr 5, 2007, at 10:08 PM, Graham Dumpleton wrote:
> FWIW, in mod_wsgi I have now added a directive which allows one to
> enable within a specific context that chunked transfer encoding should
> be used for a response when a HTTP/1.1 client is being used. Thus, if
> you know the content generate
On 03/04/07, Clark C. Evans <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 30, 2007 at 11:10:17AM +1000, Graham Dumpleton wrote:
> | One other issue if aiming at supporting chunked encoding for a request,
> | is how (if one even can) make available the trailing headers if present
> | after the final null
