6.0.0-beta1
9/2/25

[#14663] Bug with Apache mod_http2
Summary Bug with Apache mod_http2
Queue Kronolith
Queue Version Git master
Type Bug
State Not Reproducible
Priority 1. Low
Owners
Requester nd (at) syndicat (dot) com
Created 06/29/2017 (2987 days ago)
Due
Updated 06/29/2017 (2987 days ago)
Assigned 06/29/2017 (2987 days ago)
Resolved 06/29/2017 (2987 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/29/2017 10:05:03 PM Jan Schneider Comment #6
State ⇒ Not Reproducible
Reply to this comment
FWIW, I just tried the latest Apache version with mod_http2 enabled 
and didn't experience any problems with Kronolith from master branch.
06/29/2017 08:17:49 PM nd (at) syndicat (dot) com Comment #5 Reply to this comment
Horde doesn't make *any* use of HTTP/2, that's why it shouldn't be 
Horde's fault.
Ok,
may be it could makes sense to extend your docs about this if more 
users run into the same problem with current / future Apache versions) 
to disable HTTP2 within horde Virtual Hosts (as HTTP2 gets productive 
in Apache with this version and will get activated by many admins 
globally).

I.e. within VirtualHost Context:

    Protocols http/1.1

It taked me some hours to find out this, because i thought the same 
way and kronolith was the only application i've found which had any 
problems with the current Apache Version (with HTTP2 globally 
activated).

hth someone - if not, sorry for the noise...

many thanks,

Niels.


06/29/2017 07:57:02 PM Jan Schneider Comment #4 Reply to this comment
Horde doesn't make *any* use of HTTP/2, that's why it shouldn't be 
Horde's fault.
06/29/2017 07:39:53 PM nd (at) syndicat (dot) com Comment #3 Reply to this comment
How is that a bug in Kronolith?
I'm not shure, because i couldn't investigate / debug that issue much 
further. It seems that some Javascript / AJAX scripts from Kronolith 
(and only kronolith) has problems to connect to the server (some 
sockets or similiar?).

I got no error entries within the horde nor apache logs (just in kronolith).

The used Apache config is default on many distributions and i didn't 
find any other applications which seems affected under this Apache 
release - so i have to assume that Kronolith has to be "fixed" there. 
But yes - it may possible too that there is a bug in Apache or PHP / 
Apache.

Apache published that their update from 2.4.25 to 2.5.26 contains a 
lot of fixes within the HTTP2 stack and
https://www.apachelounge.com/Changelog-2.4.html

I don't know how far Horde5 is still making use of HTTP2. If it helps 
i could try to debug.

many thanks for your time,

Niels.

06/29/2017 03:42:49 PM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
How is that a bug in Kronolith?
06/29/2017 02:32:22 PM nd (at) syndicat (dot) com Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Bug with Apache mod_http2
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
Hiho guys,

after updating my apache 2.4.25 to 2.4.26 with mod_http2 loaded / 
configured /default) Kronolith stops loading events in the calendar 
views (or just load it "sporadically") while most time an error with 
the server connection is shown (red).

Tried different PHP versions and different fresh installs of Horde too.

Workaround: Disable mod_http2 for now.

hth

many thanks,
bst regards,

Niels.
http://www.syndicat.com

Saved Queries