URI refers to a static file with PATH INFO

gigaboy

gigaboy

New Member
#1
#1
I’m running OpenLiteSpeed with a static (HTML) website. I have a 404.html page set inside OLS. Once a day (seems like a bot crawl), I get these errors, where various files are appended to the end:

Code: 
2023-03-10 08:43:07.896716 [ERROR] [3470087] [172.70.100.46:38168:HTTP2-1] URI '/404.html/feed/' refers to a static file with PATH_INFO [/feed/].
2023-03-10 08:43:08.009344 [ERROR] [3470087] [172.70.100.115:45718:HTTP2-1] URI '/404.html/xmlrpc.php' refers to a static file with PATH_INFO [/xmlrpc.php].
2023-03-10 08:43:08.106873 [ERROR] [3470086] [108.162.216.54:11072:HTTP2-1] URI '/404.html/blog/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/blog/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:08.218950 [ERROR] [3470086] [108.162.216.13:27816:HTTP2-1] URI '/404.html/web/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/web/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:08.340127 [ERROR] [3470086] [172.70.100.30:48134:HTTP2-1] URI '/404.html/wordpress/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/wordpress/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:08.432207 [ERROR] [3470087] [172.70.100.143:37736:HTTP2-1] URI '/404.html/wp/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/wp/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:08.801887 [ERROR] [3470087] [108.162.216.213:55428:HTTP2-1] URI '/404.html/2020/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/2020/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:08.877386 [ERROR] [3470087] [108.162.216.135:13422:HTTP2-1] URI '/404.html/2019/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/2019/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:08.977300 [ERROR] [3470086] [172.70.100.138:59438:HTTP2-1] URI '/404.html/2021/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/2021/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:09.153999 [ERROR] [3470087] [108.162.216.135:13422:HTTP2-3] URI '/404.html/shop/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/shop/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:09.310621 [ERROR] [3470087] [108.162.216.136:29768:HTTP2-1] URI '/404.html/wp1/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/wp1/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:09.405351 [ERROR] [3470087] [172.70.100.166:11354:HTTP2-1] URI '/404.html/test/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/test/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:09.496381 [ERROR] [3470087] [108.162.216.65:31022:HTTP2-1] URI '/404.html/site/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/site/wp-includes/wlwmanifest.xml].
2023-03-10 08:43:09.594522 [ERROR] [3470087] [108.162.216.121:49652:HTTP2-1] URI '/404.html/cms/wp-includes/wlwmanifest.xml' refers to a static file with PATH_INFO [/cms/wp-includes/wlwmanifest.xml].
There are no wordpress pages, wlwmanifest, feed, or xmlrpc pages on this site.

My question: Can a rule or some other method be written that would prevent file appendages as shown in the code block? If so, how?
 
Cold-Egg

Cold-Egg

Administrator
#4
#4
I tried to customise the 404 page, but I can not reproduce the issue you shared. Do you have any special rewrite rules for the 404 situation?
 
gigaboy

gigaboy

New Member
#5
#5
In virtual host, general tab for this site, I have a 404.html page set.
HTML only site, no contexts, no htaccess.

I've been investigating the IP's and they look like they are from Cloudflare, where I push everthing through. I've tried purging the cache. I may have to escalate with them, as all the files referenced in the error block are from a wp site, not used on this site (I've checked all the page code too).
 
gigaboy

gigaboy

New Member
#6
#6
Possible Solutions which I've implemented:
- on the 404.html page itself, I changed the human clickable link to return to the homepage from "/" to the full absolute URL of the homepage.
- also deleted and reset the custom 404 page setting inside the VM | General tab. The URL now points to "/404.html" instead of the full absolute URL to the 404 page.

Watching for improvements.
 
You must log in or register to reply here.
Top