Re: [users@httpd] Mod_Status : Empty Client / Protocol / Vhost / Request Columns

On Wed, Apr 13, 2016 at 6:53 PM, Ken wrote: > I really hope that this is a bug and not "now working as intended". Thanks for reporting, fixed in [1], will propose a backport to the next 2.4 release. Regards, Yann. [1] http://svn.apache.org/r1739008

Re: [users@httpd] Mod_Status : Empty Client / Protocol / Vhost / Request Columns

On Wed, Apr 13, 2016 at 3:46 PM, Ken wrote: > The error logs contain no errors whatsoever. Using Firebug in FireFox shows > empty 's. No errors or warning appear in console either. Are you using mod_http2? Worth a test w/o it. -- Eric Covener cove...@gmail.com

Re: [users@httpd] Mod_Status : Empty Client / Protocol / Vhost / Request Columns

The error logs contain no errors whatsoever. Using Firebug in FireFox shows empty 's. No errors or warning appear in console either. All modules for Apache show they were last built on the same day 2.4.20 was upgraded. On Wed, Apr 13, 2016 at 12:23 PM, Otis DeWitt wrote:

Re: [users@httpd] Mod_Status : Empty Client / Protocol / Vhost / Request Columns

I would check the error.log file for errors. Did you have a module compile on on the previous version that is not in 2.4.20? Also inspect the web page, by right clicking on the empty spot and choose inspect then refresh your page and see what RED errors you get in the console if any. Sent from

[users@httpd] Mod_Status : Empty Client / Protocol / Vhost / Request Columns

I recently upgraded to Apache 2.4.20 on FreeBSD and up until this update, everything has been working great with mod_status. However since the upgrade, unless an action is taking place (sending reply, closing connection, etc), the Client / Protocol / Vhost / Request columns are completely blank.