We are creating this topic to protect cs-cart cart website for me and future users.
There is lot of ways to spam, hack & slowdown the website, So i request the users to submit there experience and solution to protect our websites and speed up.
I have this website link which will help to protect website from spammers.
This will also help to protect and speed up cs-cart websites.
Cs-cart is good and very fast but external things may cansumed server resources.
Our real experience with live website.
- Many bad bots are crawling, in my case some bots from singapore was crowling my site. The bot was sending more than 5000 requstes per hours. so we need to block bad bots.
- Many good bots are also crowling our website, like google, Some time google may be slow down your website, So we need to limit the the good bot also.
there are a few black and white list, bot control add-ons in the marketplace.
I’ve recommended this list of malicious crawlers for blocking several times:
I hope the author doesn’t go over to the dark side one day
Is anyone familar with how to easily add bulk bots to Alex Branding Anti Bot addon?
what is the easiest way to add all these to the root, use .htaccess?
Use bot ban by cs-commerce, its very easy to use.
@cs-commercesoftware i am using this addon, Please increase the text limit in bot ban addon.
Hello, yes, to block bots by their names you can use our bots bam addon Ban bots - addon for CS-cart
Simply add comma separated list of bots you want to blocks and thats all, addon will return to this bots HTTP 403 Forbidden header with empty page, after receive this respone bots tries few times and then they stop to new requests.
It is not a very good solution to use an add-on that works on top of CS-Cart to block bots. This is a huge overhead on the process that should be managed by the configuration of the web server itself, and a waste of server resources. Even if it works almost at the start of CS-Cart initialization, resources are still being spent on processing requests from bots.
If the web server rejects requests based solely on its configuration, the request will not be processed at all and almost zero server resources will be spent.
.htaccess only works with Apache (and Apache based) web servers. Nginx, by default, does not process .htaccess files and will only check the configuration that has been set up for it.
Anyway, the first one link from Google :
And not the first: