Looking a bit more into the httpd log files, I noticed that the client's scan for exploitable files starts with this
ibsgaarden.dk 192.168.10.115 - - [17/Nov/2014:13:08:37 +0100] "GET / HTTP/1.1" 200 5646 "-" "avast! Antivirus"
ibsgaarden.dk 192.168.10.115 - - [17/Nov/2014:13:08:37 +0100] "GET /rom-0 HTTP/1.1" 404 203 "-" "avast! Antivirus"
ibsgaarden.dk 192.168.10.115 - - [17/Nov/2014:13:08:37 +0100] "GET / HTTP/1.1" 200 5646 "-" "avast! Antivirus"
ibsgaarden.dk 192.168.10.115 - - [17/Nov/2014:13:08:38 +0100] "GET /rom-0 HTTP/1.1" 404 203 "-" "avast! Antivirus"
ibsgaarden.dk 192.168.10.115 - - [17/Nov/2014:13:08:38 +0100] "GET /cgi-bin/a2/out.cgi HTTP/1.1" 404 216 "-" "() { ignored; }; echo Constent-Type: text/html; echo ; echo ASWHDS_SCAN Infected ;"
ibsgaarden.dk 192.168.10.115 - - [17/Nov/2014:13:08:38 +0100] "GET /cgi-bin/ajaxmail HTTP/1.1" 404 214 "-" "() { ignored; }; echo Constent-Type: text/html; echo ; echo ASWHDS_SCAN Infected ;"
Then follows lots of similar attempts, all with the browser identification string "() { ignored; ..."
So maybe it's the Avast antivirus program making the scan? On their web site they announce a "Home network scanner". But then again, why are the browser identifications so strange after the first 4 attempts?