Okay - I seem to be running into problems due to empty option files. When I went through my entire setup, I entered names of option files in all the places where I would eventually be filling in information (ex: whiteListedDomains, etc). I didn't have anything to put in the file, so I only created the entry in the admin. whiteListedDomains:=controlFiles/whitelistedDomains.txt
However, I never created any file called controlFiles/whitelistedDOmains.txt. Whenever ASSP processes a connection, I get a bunch of "error" messages indicating that the option files don't exist: Nov-22-06 13:56:53 Failed to open option list file 'c:\servers\assp/controlFiles/whitelistedDomains.txt' (whiteListedDomains): No such file or directory So, to avoid all these error messages, I went in and created all the missing files, populating them just with comment lines, figuring that I'd be able to use them afterwards, and the descriptions would help out. ex: # This is the option file for the white listed domains However, I now notice / realize that ASSP is intepreting the files as being blank, and for those that are regex files, interprets this as a wildcard. For example, if I have a blank file for contentOnlyRE, ASSP pretty much bypasses all tests (PB, RBL, etc). So the question becomes should I be deleting all those empty files that contain nothing but comments and delete all the entries? Is there a reason why one can't have an empty option file? Thanks! Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
