ons 2010-09-01 klockan 22:54 + skrev Amos Jeffries:
If the de-chunker could be converted to not needing the entire object
before de-chunking that would allow us to avoid half the workaround and
extra options being proposed to get the other bits working.
You either dechunk or reject the
ons 2010-09-01 klockan 21:52 -0600 skrev Alex Rousskov:
An alternative is to add a fast ACL option to be able to enable HTTP/1.0
chunked responses to selected user agents (none by default).
+1 on that from me. Allows the chunked response support to evolve
experimentally until we feel
Alex,
The one and only known blocker to 3.1 sending HTTP/1.1 is Henriks veto.
He placed that on because the de-chunker in 3.1 required buffering the
*whole* request POST data before de-chunking or relaying on.
If the de-chunker could be converted to not needing the entire object
before
On 09/01/2010 04:54 PM, Amos Jeffries wrote:
The one and only known blocker to 3.1 sending HTTP/1.1 is Henriks veto.
He placed that on because the de-chunker in 3.1 required buffering the
*whole* request POST data before de-chunking or relaying on.
Working on it.
If the de-chunker could
