Hi Stefan,
Confirming again that your patch from Feb 4th fixed the issue. I've got now
positive feedback from my customers and have upgraded all HTTPS-sites back to
HTTP/2.
Will this patch make it into Debian Stretch?
Thanks,
Philip
Hi Stefan,
Wow, this is great! I have applied your bug915103-try2.diff patch and it seems
to fix the issue.
Only did some rudimentary testing so far. I have patched Apache for 2hrs now
and started to switch some crucial sites back to HTTP/2. Could not reproduce
the problem any more. Very nice!
Hi Stefan
Do you have any news about this? I had to downgrade the major part of my
customers to HTTP/1.1 because of this bug, which is quite a disaster.
I would greatly appreciate your help. Am also more than willing to pay you the
hours you spend on this.
Best regards,
Philip
Hi Stefan
>> On 17 Dec 2018, at 22:55, Stefan Fritsch wrote:
>>
>> Yes, that's the problematic patch, not the fix.
>>
>> I have some hope that the fix for the issue is this upstream commit:
>> https://svn.apache.org/viewvc?view=revision=1843468
>>
>> It would be nice if you could apply the
Hi Stefan
> On 17 Dec 2018, at 22:55, Stefan Fritsch wrote:
>
> Yes, that's the problematic patch, not the fix.
>
> I have some hope that the fix for the issue is this upstream commit:
> https://svn.apache.org/viewvc?view=revision=1843468
>
> It would be nice if you could apply the attached
> Could you please shed light on where I can find commit
> bee2facd9343beda10677b139cd9b2e49e986f01 for Debian Stretch?
> I did not find apache2 sources on https://salsa.debian.org - Where is the
> official Debian apache2 source git repo?
> If it is not public, please attach the patch.
>
> We
> i'm still wrong:
> da1d372d0d58474f2f5a71b9acd301abf9b11bc0 is the commit on the master branch
>
> On the stretch branch, the commit
> is bee2facd9343beda10677b139cd9b2e49e986f01
Hi Cyr
Could you please shed light on where I can find commit
bee2facd9343beda10677b139cd9b2e49e986f01 for Debian
> fdz96WVxhTopdug4Yu6T6nwmnFebsV90DtTQvdvPJdDumDoMp9docGx80ypkj/zE
> fDJchBn2lb2x4m8+M8kcnlm/5+/yPyjMOd0Tlk3XdJxUQX6+/Dod/cqk4ooB+hdy
> 7pjgFqBkDBu0fSktMFe2nfedTM4PUqy1BXLb42u3a3/FWaoCNK4HXsN7vbUgQQcN
> FagHrjJ1dk/GqWgoYKeE4DOsdStJxZLL7ueSvl8x49DcQnZHYEtem0DXDrRKICOD
> bK45JpDFcO8gwaGQFNhcn
Package: apache2-bin
Version: 2.4.25-3+deb9u4
Severity: important
Tags: patch upstream
Dear Maintainer,
We got a lot of such segfaults in error.log, provoked by mod_proxy_fcgi:
[core:notice] [pid 43086:tid 139897736885440] AH00051: child pid 43114 exit
signal Segmentation fault (11)
As
Dear maintainer,
I would greatly appreciate if you could push this fix into current Debian
Stretch. The problem still persists in Cyrus-imapd 2.5.10-3 and above patch
from upstream fixes it. After having upgraded a mailserver to Debian Stretch we
had a massive amount of negative customer
10 matches
Mail list logo
