This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 1640 [details] web page shows error Hello, I am getting this error on the browser: [an error occurred while processing this directive]. See attached screenshot. The web server error log shows following error: [Wed Mar 16 16:21:07.179929 2016] [include:error] [pid 16232] [client 127.0.0.1:47093] AH01337: Could not parse expr "$debug = 1" in /usr/local/src/markup-validator/htdocs/header.html: Parse error near '$', referer: http://validator.pakphp.com/w3c-validator/check [Wed Mar 16 16:21:07.180010 2016] [include:error] [pid 16232] [client 127.0.0.1:47093] AH01337: Could not parse expr "$feeds = 1" in /usr/local/src/markup-validator/htdocs/header.html: Parse error near '$', referer: http://validator.pakphp.com/w3c-validator/check [Wed Mar 16 16:28:31.803677 2016] [include:error] [pid 16296] [client 127.0.0.1:47119] AH01337: Could not parse expr "$QUERY_STRING = /(^|[;&])debug(=[^0]?)?(\\b|$)/" in /usr/local/src/markup-validator/htdocs/header.html: Parse error near '$' [Wed Mar 16 16:28:31.803939 2016] [include:error] [pid 16296] [client 127.0.0.1:47119] AH01337: Could not parse expr "$includeJS = 1" in /usr/local/src/markup-validator/htdocs/header.html: Parse error near '$' The webserver is apache 2.4. It is running on Debian Jessie and has a private ip. It seems some of the server side include statements given in header.html are not being processed correctly by the webserver. The statements containing variables are given errors. I got rid of the error by entering following line in header.html: <!--#config errmsg="" -->. I used this link for reference: http://httpd.apache.org/docs/current/howto/ssi.html Thanks, Nadir Latif