The workaround is for now OK for me if I don't face anything be broken now. And as the last option I can also switch back to 2.4.25 and have my working instance again, it's just a symlink change ;) But I prefer to run 2.4.26 with the directive set cause of the HTTP/2 changes in 2.4.26.
Regards, Am 27.06.2017 um 22:48 schrieb Jacob Champion:
On 06/27/2017 01:42 PM, rockzOr wrote:Is there a plan for releasing 2.4.27 as for the broken behaviour or will it be next regular release in X months?Bill had a good answer in another thread [1]: On 06/27/2017 10:15 AM, William A Rowe Jr wrote:We don't generally try to predict our release schedule, when it's baked we publish a release. But Jim and Jacob are furiously updating the test framework as you were asking your question, so I'm guessing the group will be working to release this fix just as soon as it is agreed upon, within a week or few.--Jacob[1] https://lists.apache.org/thread.html/e7c63db48d314c55b33cf5185166ed97fc2a8b797159072ecbeaf9d7@%3Cdev.httpd.apache.org%3E--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|