Arrow Trader 5

Installation Guides
Admin Modules
References

Arrow Trader Core

Installation Guides
Admin Modules
References

Arrow Trader eXtreme V2

Installation Guides
Admin Modules
References

Arrow Trader eXtreme V1

Installation Guides
Admin Modules
References

Arrow Trader Lite 3

Installation Guides
Admin Modules
References

Q&A

Getting started

Search

The Site Compliance Spider is a very handy tool to keep bad trades out by not letting them sign-up
in the first place. The SCS loads every trade and checks the source to see if it violates any rules.




spider 1 - http status codes
When apache replies to a request made by a client, it sends a lot more info that you normally see. One of the things apache sends is the status code of the page that was requested. The status code tells your browser the state the requested page is in. For example, it may not exist anymore, it may be restricted, it may be moved, it may be overloaded, etc. the SCS can read these codes and filter out all trades with bad codes. For a complete overview, click here. The most powerful feature of the SCS is of course that it's able to pick up trades that are redirecting hits, experiencing server errors, etc.




If you wish, you can let the SCS run once every 12 hours. It will check all your trades, write a report and mail you the url to this report, so you can review your trades.
Cron Spider: turn this on to let the cron run the spider once every 12 hours. No adjustments to the crontab are needed.
Cron Mailer: select when you would like to receive a mail from the cron spider. Because the cron spider runs only 2 times a day, you can leave this to 'always send mail'. It won't flood your mailbox.
local path for html reports: the cron spider writes a report every 12 hours about all the trades that violate any rules. Here you need to specify where the reports should be written to. Make sure that the path is accessible via the web!
url to root directory of html reports: this is where you fill in the url to the directory where the spider writes the reports to. For example, if the local path is /usr/www/yoursite.com/htdocs/atx-spider/ then the url is http://www.yoursite.com/atx-spider/. Also make sure that the directory /atx-spider/ in this case has the correct permissions. If you're not sure what they should be, start with 777.



Click this button right now to let the SCS spider all your trades and output the results. If some of your sites are slow this might take a while. But in most cases never more than 1 - 10 seconds.




Via this form you can spider any site, trade or no trade. This is handy when you want to test the SCS or when you want the SCS to check a new site before you add it as a trade for example.




Here's an example of the report of the SCS when it was ordered to spider all trades. It only displays those trades that violate a rule. As you can see, none of these trades had the string "bitchlinks.com" in their source, so they don't have any hardlinks.

note
At this moment (ATX v1.0), the SCS is a report-tool only!
It will not disable any trades that are violating rules. It will however prevent trades from signing up if they are violating any rules when they are trying to signup. In a future version of ATX the SCS will be able to (optionally and temporarily) disable trades again.
Help us improve our articles by rating them
- This article is -

Too long & complicated

Too short & simple

Not relevant enough

Just about right
3999