Last modified: 2014-10-10 14:55:05 UTC
Seeing a flood of these errors in fluorine:/a/mw-log/apache2.log: Sep 30 22:24:17 mw1018: [proxy_fcgi:error] [pid 12557] [client 10.64.0.103:5054] AH01070: Error parsing script headers, referer: https://es.wikipedia.org/wiki/Estadio_Coloso_del_Ruca_Quimey Sep 30 22:24:16 mw1019: [proxy_fcgi:error] [pid 30172] [client 10.64.0.105:52919] AH01068: Got bogus version 1, referer: https://commons.wikimedia.org/wiki/File:Bibliotheque_de_Toulouse_-_Pic_d-Aneto_(pd).jpg Sep 30 22:24:16 mw1019: [proxy_fcgi:error] [pid 30172] (22)Invalid argument: [client 10.64.0.105:52919] AH01075: Error dispatching request to :, referer: https://commons.wikimedia.org/wiki/File:Bibliotheque_de_Toulouse_-_Pic_d-Aneto_(pd).jpg
According to httpd[1] "Got bogus version 1" refers to the first byte in every fastcgi record. Per the spec[2] the only valid value there is 1. Something odd is going on, but without a capture of the packets i couldn't say what. [1] https://github.com/apache/httpd/blob/trunk/modules/proxy/mod_proxy_fcgi.c#L525 [2] http://www.fastcgi.com/devkit/doc/fcgi-spec.html#S3.3
So, both these lines of errors have been showed to be basically bogus. I think the only way to filter/silence them is to patch apache directly. @Erik: never look at trunk for apache sources, but to our specific version, which is 2.4.7 The only way to make these alarms go away is to backport patches that corrected logging. IDK if we want to invest that kind of time in such an activity.
https://issues.apache.org/bugzilla/show_bug.cgi?id=52879
