[Tickets #14663] Re: Bug with Apache mod_http2

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14663
------------------------------------------------------------------------------
  Ticket           | 14663
  Aktualisiert Von | nd at syndicat.com
  Zusammenfassung  | Bug with Apache mod_http2
  Warteschlange    | Kronolith
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


nd at syndicat.com (2017-06-29 19:39) hat geschrieben:

> 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.