Hi Stefan >> On 17 Dec 2018, at 22:55, Stefan Fritsch <s...@sfritsch.de> 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&revision=1843468 >> >> It would be nice if you could apply the attached patch to the debian source >> package, rebuild it, and check if it fixes the issue. Thanks. > > Thanks a lot for that patch. I have applied it to apache2 2.4.25-3+deb9u6, > compiled apache2 using dpkg-buildpackage, and installed apache2-bin package > on production webserver. So far no issues. > But I cannot tell you if it improved anything. The thing is, I couldn't > reproduce the previous issue under desktop Safari right before patching > Apache. I tried hard to reproduce it the same way I was able to reproduce it > on Dec 14th. I switched back the relevant sites to HTTP/2 (Protocols h2 > http/1.1) and tested in Safari checking web inspector console on a site where > previously a bunch of jpg images were not loaded at all. > So, it seems that magically, the problem went away by itself. Could the > original issue be related to any load / buffer issues on long running apache?? > I am sorry that I cannot give you any more detailed feedback. It works fine > with your patch as it did before...
I need to disappoint you. I was now able to reproduce the same issue under Apache with applied patch. It was only a Safari browser caching thing why I couldn't reproduce it before. After emptying browser cache the problem occurred again. Switching back to http/1.1 resolves the issue. So it looks like your patch did not change anything here. Looking forward for your next trick! Cheers, Philip