search engines and crawler known to be evil 19.2 Basic input validation against vulnerability attacks 19.3 Admin backend protection against remote access 19.4 Log file reporting attempts to abuse Sphider-plus 20. Bound database 21. Suggest framework 22. Integration of Sphider-plus into existing sites 22.1 Integration into existing site by use . . .
. . .
Re-indexing of all sites, or site specific, started periodically at a defined time interval. In Admin backend the time interval is selectable to 3 hours, 12 hours, 1 day, 1 week or 1 month. Also the count of periodically performed re-indexing procedures could be defined in Admin backend. Once started, the Re-index procedures will . . .
. . .
'Statistics' menu called 'Auto Re-index log file'. The periodical Re-indexer could be started and aborted in Admin backend, by selecting the 'Periodical Re-index' submenu in 'Sites' view. Instead for site individual Re-indexing, the periodical Re-indexer could be started and aborted in the "Options" menu of each site. 2.5 Preferred Re-indexing . . .
. . .
started and aborted in the "Options" menu of each site. 2.5 Preferred Re-indexing Each new URL added to the Admin backend, could be supplied with a priority level. This level will be used by the option 'Re-index only preferred sites'. Level 1 will be interpreted as most important, while level 5 should be used for non-prioritized sites. In case . . .
. . .
option is not available for Intranet and all 'localhost' applications. In 'Sites' view of the Sphider-plus admin backend you may check ability of this web service. Also required time (seconds) to create one thumbnail is presented. So you may decide, whether you like to use this web service for all pages to be indexed. More details are described . . .
. . .
web service, this option is not available for Intranet and all 'localhost' applications. To be activated in Admin backend, this service additionally requires an individual key. To be signed up at Google. More details are described in the readme.pdf documentation. 2.9 Follow Sitemap file To be activated in Admin settings, Sphider-plus will use . . .
. . .
sitemap. Foreseen to hold a subset of the global sitemap, this optional selection in ‘Settings’ menu of the admin backend may be used to index only often modified pages of a site. Useful to fasten the index procedure by concentrating only on new page content. The private Sphider-plus sitemaps are always expected in the root folder of the site to . . .
. . .
download, the two files 'must include.txt' and 'must_not_include.txt' are empty. While calling 'Settings' in admin backend and enabling in section 'General Settings' the option: Store global values of string lists 'Must include' and 'Must Not include' for all URLs And afterwards pressing any 'Save' button, the content of these files are . . .
. . .
appear using this search mode. In order to limit the amount in the result listing, there is an option in the admin backend named Define maximum count of result hits for queries with wildcards To be found in ‘Settings’ = ‘Search Settings’. If you like to know the multiple words found in the database to be highlighted: In your editor open the . . .