On Mon, Jun 2, 2025 at 1:25 PM Ruediger Pluem wrote:
>
> On 5/22/25 3:29 PM, jean-frederic clere wrote:
> > On 5/22/25 2:37 PM, Yann Ylavic wrote:
> >> On Thu, May 22, 2025 at 9:39 AM jean-frederic clere
> >> wrote:
> >>>
> >>> On 5/20/25 2:48 PM, Yann Ylavic wrote:
> On Tue, May 20, 2025 a
On 5/22/25 3:29 PM, jean-frederic clere wrote:
> On 5/22/25 2:37 PM, Yann Ylavic wrote:
>> On Thu, May 22, 2025 at 9:39 AM jean-frederic clere
>> wrote:
>>>
>>> On 5/20/25 2:48 PM, Yann Ylavic wrote:
On Tue, May 20, 2025 at 12:03 PM jean-frederic clere
wrote:
>
> Find the c
On 5/22/25 2:37 PM, Yann Ylavic wrote:
On Thu, May 22, 2025 at 9:39 AM jean-frederic clere wrote:
On 5/20/25 2:48 PM, Yann Ylavic wrote:
On Tue, May 20, 2025 at 12:03 PM jean-frederic clere wrote:
Find the configuration I have used to reproduce the customer issue,
thanks for all explanatio
On Thu, May 22, 2025 at 9:39 AM jean-frederic clere wrote:
>
> On 5/20/25 2:48 PM, Yann Ylavic wrote:
> > On Tue, May 20, 2025 at 12:03 PM jean-frederic clere
> > wrote:
> >>
> >> Find the configuration I have used to reproduce the customer issue,
> >> thanks for all explanations for far ;-)
> >
On 5/20/25 2:48 PM, Yann Ylavic wrote:
On Tue, May 20, 2025 at 12:03 PM jean-frederic clere wrote:
Find the configuration I have used to reproduce the customer issue,
thanks for all explanations for far ;-)
So regression is on vhost "host14.example.com" right? And not
"fproxy.example.com"?
On Tue, May 20, 2025 at 12:03 PM jean-frederic clere wrote:
>
> Find the configuration I have used to reproduce the customer issue,
> thanks for all explanations for far ;-)
So regression is on vhost "host14.example.com" right? And not
"fproxy.example.com"?
Cheers;
Yann.
On 5/19/25 9:05 PM, Ruediger Pluem wrote:
On 5/19/25 8:13 PM, Yann Ylavic wrote:
On Mon, May 19, 2025 at 7:42 PM Yann Ylavic wrote:
On Mon, May 19, 2025 at 5:47 PM Ruediger Pluem wrote:
On 5/19/25 5:27 PM, Yann Ylavic wrote:
On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
wrote:
On 5/19/25 8:13 PM, Yann Ylavic wrote:
> On Mon, May 19, 2025 at 7:42 PM Yann Ylavic wrote:
>>
>> On Mon, May 19, 2025 at 5:47 PM Ruediger Pluem wrote:
>>>
>>> On 5/19/25 5:27 PM, Yann Ylavic wrote:
On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
wrote:
>
>> Am 19.05.
On Mon, May 19, 2025 at 7:42 PM Yann Ylavic wrote:
>
> On Mon, May 19, 2025 at 5:47 PM Ruediger Pluem wrote:
> >
> > On 5/19/25 5:27 PM, Yann Ylavic wrote:
> > > On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
> > > wrote:
> > >>
> > >>> Am 19.05.2025 um 16:46 schrieb Yann Ylavic :
> > >>
On Mon, May 19, 2025 at 5:47 PM Ruediger Pluem wrote:
>
> On 5/19/25 5:27 PM, Yann Ylavic wrote:
> > On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
> > wrote:
> >>
> >>> Am 19.05.2025 um 16:46 schrieb Yann Ylavic :
> >>>
> >>>
> >>> Hm, r1912459 added this test to disable reuse for CONNEC
On 5/19/25 5:27 PM, Yann Ylavic wrote:
> On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
> wrote:
>>
>>> Am 19.05.2025 um 16:46 schrieb Yann Ylavic :
>>>
>>>
>>> Hm, r1912459 added this test to disable reuse for CONNECT connections
>>> to ProxyRemote, because I thought that CONNECT reque
> Am 19.05.2025 um 17:27 schrieb Yann Ylavic :
>
> On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
> wrote:
>>
>>> Am 19.05.2025 um 16:46 schrieb Yann Ylavic :
>>>
>>>
>>> Hm, r1912459 added this test to disable reuse for CONNECT connections
>>> to ProxyRemote, because I thought that
On Mon, May 19, 2025 at 4:54 PM Stefan Eissing via dev
wrote:
>
> > Am 19.05.2025 um 16:46 schrieb Yann Ylavic :
> >
> >
> > Hm, r1912459 added this test to disable reuse for CONNECT connections
> > to ProxyRemote, because I thought that CONNECT requests were not
> > reusable.
>
> Hmm, what kind o
> Am 19.05.2025 um 16:46 schrieb Yann Ylavic :
>
> On Mon, May 19, 2025 at 4:05 PM Ruediger Pluem wrote:
>>
>>
>>
>> On 5/19/25 1:53 PM, jean-frederic clere wrote:
>>> Hi,
>>>
>>> While investigating a customer case I note a regression with forward proxy.
>>> While testing I have:
>>> 2.4
On Mon, May 19, 2025 at 4:05 PM Ruediger Pluem wrote:
>
>
>
> On 5/19/25 1:53 PM, jean-frederic clere wrote:
> > Hi,
> >
> > While investigating a customer case I note a regression with forward proxy.
> > While testing I have:
> > 2.4.57 finished in 3.05s, 3278.62 req/s, 743.70KB/s
> > 2.4.x fin
On 5/19/25 1:53 PM, jean-frederic clere wrote:
> Hi,
>
> While investigating a customer case I note a regression with forward proxy.
> While testing I have:
> 2.4.57 finished in 3.05s, 3278.62 req/s, 743.70KB/s
> 2.4.x finished in 15.38s, 650.17 req/s, 147.88KB/s
>
> The regression goes way
Hi,
While investigating a customer case I note a regression with forward
proxy. While testing I have:
2.4.57 finished in 3.05s, 3278.62 req/s, 743.70KB/s
2.4.x finished in 15.38s, 650.17 req/s, 147.88KB/s
The regression goes way with:
+++
jfclere@fedora:~/httpd-2.4.x$ svn diff .
Index: module
17 matches
Mail list logo