kimmik wrote:[Sat Oct 25 20:54:20.994842 2014] [include:error] [pid 4540:tid 1780] [client 127.0.0.1:62722] unable to include potential exec "include/bottom.html" in parsed file C:/XAMPP/apache/error/HTTP_NOT_FOUND.html.var, content type not text/*
[Sat Oct 25 20:54:20.995843 2014] [include:error] [pid 4540:tid 1724] [client 127.0.0.1:62726] unable to include potential exec "include/top.html" in parsed file C:/XAMPP/apache/error/HTTP_NOT_FOUND.html.var, content type not text/*
After many wasted hours I think I have got to the bottom of this mess. Perusing the access logs and error logs and the fact that these errors were generated on every page request - even a simple html blank page (no images, css, includes, js)
I have come to the conclusion that these requests for files from the XAMPP Apache directories are a result of
127.0.0.1 - - [08/Nov/2014:10:33:46 +0000] "GET /favicon.ico HTTP/1.1" 200 5567
in the access log.
The file favicon.ico does not exist in the project base htdocs directory (this is the last thing we are interested in when developing a web app) However, if a favicon.ico file is placed in the base htdocs directory the errors seem to stop.
So I guess that is a "work around" to the issue rather than a genuine solution and the mystery of why the errors (or more to the point why Apache is generating errors to something it cannot find in its own directories) remains a fault.
Still, I thought that posting the work around may be of some assistance to others, and might save them some time.