However, I know Proxomitron is able to do filtering (changing/inserting/deleting) of ssl html, js etc.
For example, I have a filter set up for bugzilla (sample bug) which inserts a call for a local stylesheet, to tweak the appearance and (imo) make it easier to read.
Proxomitron has a number of functions, including essentially re-writing webpages before presenting them to the browser. This can involve both security/privacy issues (eliminating webbugs, exploits, etc) and “eye-candy”/usability issues, like my bugzilla example.
The typical form of a web filter is to analyse the page, looking for an expression, which is replaced in the page sent to the browser.
This is an example of a web bug filter, by hpguru:
Name = "Block Web Bugs - hp2"
Active = TRUE
Bounds = "<img *>"
Limit = 512
Match = "*src=\w*"
"& (*(height=("|)[#1-4])\1)"
"& (*(width=("|)[#1-4])\2)"
Replace = "<img src="http://Local.ptron/wbani.gif" \1 \2 alt="Web Bug">"
Some are far more complex. So, in the case of Proxomitron, analysis is taking place.
It makes sense to first check the data stream from the web and than(!) give it to the browser. Otherwise the browser save the data (latest step for avast to check the data, but this is what webshield (I think) don´t want, it will be scan all before it is saved)) … and if the data will be scanned after the browser has saved it (and maybe let standard shield don´t find a virus for example in a .js file) than the browser will use it and infect the system … or something like that.
That was a bad and fast idea of me.
Ouh … sorry it was a joke.
I wasn´t angry or something like that.