On Dec 18, 2015 6:23 AM, "Klaus Darilion" <[email protected]> wrote: > > For the records: Since we use Apache 2.4.17 we do not have that problem > anymore.
Excellent! Glad that seems to have solved it. Thanks for reporting back. --Jacob [on mobile; sorry for any formatting annoyances]
