CodeIgniter Forums

Full Version: 404 Page Not Found—> assets in log files
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have enabled errors to be logged and my site is running perfectly fine but i am always gettings these errors in my log files.

Code:
ERROR - 2015-01-22 15:27:42—> 404 Page Not Found—> assets
ERROR - 2015-01-22 15:44:22—> 404 Page Not Found—> admin
ERROR - 2015-01-22 16:22:03—> 404 Page Not Found—> vtigercrm

Please guide me why these errors are been logged and how can i prevent it. Thanks
Maybe someone was going just playing around and entering things into the URL in the browser to see if they work? Like http://yoursite.com/admin to see if something interesting pops up?
(01-26-2015, 02:37 PM)CroNiX Wrote: [ -> ]Maybe someone was going just playing around and entering things into the URL in the browser to see if they work? Like http://yoursite.com/admin to see if something interesting pops up?

I thought so as well, but it didn't just happen once or twice. I get these errors daily in log files.

Today's log so far:

PHP Code:
ERROR 2015-01-26 22:55:20 --> 404 Page Not Found --> vtigercrm 
It happens because like it was mention before either someone or most likely an indexing bot or evil bot is visiting your site trying to find exploits or previous links.

But most likely is a bot whether is from a search engine or someone trying to look for an exploits on your site they are just in a way testing to see if anything returns.

admin, admincd, testing, assets, etc... are very popular destinations for control panels and other things.

In reality is not an error that you have to worry about CI is just telling you that someone is visiting that route and it doesn't exists.

What can you do? you can be creative, like using an htaccess file to route those routes, or you can create a routing control and in your routes file just add those routs that don't exist and rout them to go back to your home page, or turn off error reporting in the config file.

Depending on who is visiting your none existing pages I would utilize them to get more traffic to my existing pages by either a redirect in a controller or a cool 404 letting those visitors know that the page that they are looking no longer exist and give them some cool urls to go to on my website.

Now if they are evil bots or spider bots then I would just block them through htaccess.

But is up to you on what you want to do, aside from that you really can't do much there will always be a dead link on a site and whether CI is cathing the error or not your server is.