On Wed, Jul 9, 2014 at 2:12 PM, Graham Leggett wrote:
> On 9 Jul 2014, at 11:56, Yann Ylavic wrote:
>
>> On Wed, Jul 9, 2014 at 7:35 AM, Marion & Christophe JAILLET
>> wrote:
>>> Just a few details :
>>>
>>>1) Shouldn't we use 100-continue (lowercase c) instead, to more closely
>>> match htt
On 9 Jul 2014, at 11:56, Yann Ylavic wrote:
> On Wed, Jul 9, 2014 at 7:35 AM, Marion & Christophe JAILLET
> wrote:
>> Just a few details :
>>
>>1) Shouldn't we use 100-continue (lowercase c) instead, to more closely
>> match http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html, § 8.2.3 ?
>
On Wed, Jul 9, 2014 at 12:56 PM, Yann Ylavic wrote:
> On Wed, Jul 9, 2014 at 7:35 AM, Marion & Christophe JAILLET
>> 3) // fast path, should be /* fast path */
>
> Thanks, will fix it.
Done in r1609100 (2.4.x) and r1609101 (trunk).
On Wed, Jul 9, 2014 at 7:35 AM, Marion & Christophe JAILLET
wrote:
> Just a few details :
>
> 1) Shouldn't we use 100-continue (lowercase c) instead, to more closely
> match http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html, § 8.2.3 ?
>This would also be consistent with the use of
Le 08/07/2014 15:16, j...@apache.org a écrit :
Author: jim
Date: Tue Jul 8 13:16:27 2014
New Revision: 1608762
URL: http://svn.apache.org/r1608762
Log:
Merge r1588519 from trunk:
mod_proxy: When ping/pong is configured for a worker, don't send or forward
"100 Continue" (interim) r