Hi,

Picked up three '404's from the web server logs, and I'm simply interested in what these website abuse attempts were trying to do. The url's were:

http://www.example.com/templates_c/<?php echo $this->_tpl_vars['xoops_imageurl']; ?>logo.gif

http://www.example.com/templates_c/<?php echo $this->_tpl_vars['xoops_url']; ?>/xoops.css

http://www.example.com/templates_c/<?php echo $this->_tpl_vars['xoops_themecss']; ?>

Obviously they found out the site is running XOOPS, and there is a /templates_c path, but they won't be able to pass PHP code like like, a bit like attempting a passthru.

Sigh, ... some people have got nothing better to do. LOL

Peter

......templates_c always exist on XOOPS it is like the chache lol

Hi,

Quote:

Yes, I did already state...

Quote:

and I know what the path is for, but my subject, is a question.

Peter

I'm pretty new to Xoops, but have used PHP-Nuke for years. In the log in PHP-Nuke, 404 Page errors can be someone fishing for ways to hack, but quite unlikely. It's probably more to the fact that the person trying to login to your site using the cache was for some reason unable to load the page they previously were on.

Could be a number of reasons:

server popular and bandwidth could have been stretched or the user is using a slow machine and timed out before they were able to load the screen.

An idea to stop these from happening is to bounce users directly from a 404, 403 and even 500 Error Page straight to your Homepage.

This can be configured quite easily using CPanel. I believe .htaccess is able to do this as well.

Hope that helps

Since Smarty translates Smarty tags into PHP, it could very well be errors in pages (not completely loaded etc.) that generate these 404 errors. So not by definition done by hackers.

Herko