mån 2010-08-16 klockan 14:08 -0600 skrev Alex Rousskov:
> Should we try implement what you described then? In summary:
>
>- If the next hop is known to be 1.1, send a chunked request.
>- Otherwise, try to accumulate the full body, with a timeout.
> Send 411 if we timed out while accu
On 08/16/2010 01:52 PM, Henrik Nordström wrote:
mån 2010-08-16 klockan 13:30 -0600 skrev Alex Rousskov:
Since Squid is a program and not a human being, we do need to hard-code
a single default. Clearly, there will be ACLs to change the behavior,
but if no options apply, we still need to do some
mån 2010-08-16 klockan 13:30 -0600 skrev Alex Rousskov:
> Since Squid is a program and not a human being, we do need to hard-code
> a single default. Clearly, there will be ACLs to change the behavior,
> but if no options apply, we still need to do something.
>
> Yu have more-or-less said "no"
On 08/16/2010 01:17 PM, Henrik Nordström wrote:
mån 2010-08-16 klockan 11:43 -0600 skrev Alex Rousskov:
I am revisiting this issue in hope to enable HTTP/1.1 to clients. If
Squid properly dechunks requests on the client side, what should happen
to that dechunked request on the server side? Let'
mån 2010-08-16 klockan 11:43 -0600 skrev Alex Rousskov:
> I am revisiting this issue in hope to enable HTTP/1.1 to clients. If
> Squid properly dechunks requests on the client side, what should happen
> to that dechunked request on the server side? Let's start with the most
> general case were
