On Thu, Jul 11, 2013 at 10:15 PM, Greg Stein wrote:
> Hey all,
>
> Right now, trunk and the 1.8.1 backport request implements the following
> option:
>
> http-detect-chunking = off / default: perform no detection. A 411
> response will throw an error message suggest to turn this option on.
>
I'm
> -Original Message-
> From: Ben Reser [mailto:b...@reser.org]
> Sent: vrijdag 12 juli 2013 20:40
> To: Philip Martin; Greg Stein; Subversion Development
> Subject: Re: Tri-state for http-detect-chunking config option
>
> On Fri, Jul 12, 2013 at 10:48 AM, Stefan Sp
On Fri, Jul 12, 2013 at 10:48 AM, Stefan Sperling wrote:
> On Fri, Jul 12, 2013 at 06:41:13PM +0100, Philip Martin wrote:
>> Stefan Sperling writes:
>>
>> > So I think we should just accept the penalty of an extra request in 1.8.
>> > And perhaps have a knob to turn auto-detection off if users re
On Fri, Jul 12, 2013 at 06:41:13PM +0100, Philip Martin wrote:
> Stefan Sperling writes:
>
> > So I think we should just accept the penalty of an extra request in 1.8.
> > And perhaps have a knob to turn auto-detection off if users really care
> > about a bit of extra latency.
>
> That sounds li
Stefan Sperling writes:
> So I think we should just accept the penalty of an extra request in 1.8.
> And perhaps have a knob to turn auto-detection off if users really care
> about a bit of extra latency.
That sounds like "http-chunked-requests=auto|yes|no" with auto being the
default. Is there
On Fri, Jul 12, 2013 at 2:08 AM, Ben Reser wrote:
> On Thu, Jul 11, 2013 at 7:15 PM, Greg Stein wrote:
>...
>> I believe the bigger point with tri-state is the change of the
>> *default* from "assumed chunked-request capability" to "perform
>> detection".
>>
>> For 1.9.x, I would be +1 on a defau
On Thu, Jul 11, 2013 at 10:15:34PM -0400, Greg Stein wrote:
> That leaves the 1.8.1 release. There are several possibilities here:
My opinion is:
We've switched from neon to serf. Serf needs chunked requests
for some future features, neon didn't. That's fine, but serf should
send an extra request
On Thu, Jul 11, 2013 at 7:51 PM, Daniel Shahaf wrote:
> In tristate, the default is "auto". The error message that mentions "no" only
> appears for people who explicitly set "yes" (that is, changed the default)
> *and* ran into a bad proxy. I think we can assume that people who set "yes"
> know
On Thu, Jul 11, 2013 at 7:15 PM, Greg Stein wrote:
> My current concern with the tri-state is people who set "=no". They
> will permanently degrade to C-L requests. That is problematic today,
> and especially as ra_serf advances. If the server admin upgrades to a
> chunked-enabled proxy, the clien
On Thu, Jul 11, 2013 at 10:15:34PM -0400, Greg Stein wrote:
> The tri-state switches this to:
>
> = auto / default: send an extra OPTIONS. like "on" above.
>
> = yes: no delivery of OPTIONS. presume chunked is allowed.
>
> = no: no delivery of OPTIONS. only use C-L, as chunked is presumed
10 matches
Mail list logo
