The Base Config 090320

[lnminente]

Hi Siamesecat,
-Strange characters in my own english means Odd chars hehehe, i will change it, thanks!

-The filters with a lot of NNNNN are only separators, with the open window you will see they have no code, only (^?) or text.

- There are 4 filters, for loging request or incoming connections, and for images or for non images. All of them are intented to have the log window opened with HTTP headers loging unticked, replacing them with only the most important info. The filter to log requesting non images, wich is the only one enabled by default, will write in the log window a green line with the most important request we would need to see. We will see there when we are downloading a video, a sound, a javascript, a flash, etc
In Log requests, the condition is $TST(imgExt=*), to see what extensions are intended to be images in the actual or a future base config open it with a text editor and search for "$SET(imgExt=". In this version, you will find $TST(uExt=png|gif|ico|jpg)$SET(imgExt=1)
I only added the typical web image extensions.

The filter to "Log incoming images" is disabled by default it is ther only as complementary to the "log non images". They work having in consideration the imgExt and if the incoming http header Content-Type is equal to image/*. Both of the "log incoming" filters are useful for debugging purposes when we are writing a header filter for example to block some requests.

Of course i will log anything that is not an image, the non images are the most important to me, maybe you thought log was "log to a file". BTW to mean "log to a file" i write "logF" in the title of the filter.

-The protect list is a header filter needed for my ad filters to give more confort to add exceptions. All the matched webfilters for ad links, flash objects, iframes, scripts, will have two links, the first for toggle and the second to add to the protect list.

NOTE: I will be updating the first post, with the questions/answers from this post