You get the errors using Chrome? What does Firefox say? There is one new feature in 2.4.25, off by default, that causes such errors with Chrome. The Chrome bug report has status "fixed", not sure when it will be released (https://bugs.chromium.org/p/chromium/issues/detail?id=662197).
As I said, this behaviour is off by default for this reason. It is changed by directive "H2EarlyHints". But maybe it's something totally unrelated to this. Are you able to reproduce this on a non-production server of yours? Thanks, Stefan > Am 01.01.2017 um 23:23 schrieb Helmut K. C. Tessarek <tessa...@evermeet.cx>: > > I'm sorry that the previous mail was so short, but there are no error > messages in the error log. It happens on several subdomains and for > aliases within the same domain, which makes no sense to me, especially > since I never came across this problem with the previous httpd version. > > I'm using the following directive: Protocols h2 http/1.1 > > I had to deactivate h2 altogether, because a lot of subdomains and > aliases errored out and were not reachable. I could have also reverted > back to 2.4.23, which I will probably do in a couple of days. > > I couldn't do any problem determination on my production server. I had > to make it work asap. > > I just wanted to mention that there's something off with h2. > > Since I only upgraded httpd from 2.4.23 to 2.5.25 w/o changing any > configuration files, it must be a problem with the current h2 > implementation. > > Cheers, > K. C. > > -- > regards Helmut K. C. Tessarek > lookup http://pool.sks-keyservers.net for KeyID 0xC11F128D > > /* > Thou shalt not follow the NULL pointer for chaos and madness > await thee at its end. > */ Stefan Eissing <green/>bytes GmbH Hafenstrasse 16 48155 Münster www.greenbytes.de
