Post Reply 
"off-site" blockers
Feb. 05, 2015, 12:28 PM
Post: #1
"off-site" blockers
this topic came up in a thread on SSL connections...
basically, as a generality, here's what happens -

..1) i'm browsing ht-tp://A.com while using "Half-SSL"
..2) the browser pops up a [email protected] "security alert, do you want to continue" - NO, i do NOT !!!
......a) for one, i'm not even browsing a SSL site
......b) for two, it's 'coded' in such a way that it 'snuck past' "Half-SSL"
......c) something is trying to come in from ht-tpS://B.com

monitoring this over the last few days, i've found that dang near ALL of these occur due to CSS...
an example - http://bclund.tumblr.com/post/1101441457...nny-in-the

"Half-SSL" does correct the issue of the CSS coming in from ht-tpS...
BUT something "inside" the CSS is what 'breaks' "Half-SSL"...

of course do note that i block .js by default and we already have a way to block 3rd Party .js...


now, there are two schools of thought on how to "correct" this by rewriting the code with Proxo -

..1) attempt to fix what's "inside" the CSS that was originally coming in under SSL but "Half-SSL" already fixed it to come in under non-SSL
..2) just block the entire CSS and let the chips fall where they may


i attempted method #1 for weeks on end many months ago - nothing but a futile chase with no end in sight...
just too many CSS "tricks" to try to get one filter to catch all of...

so i ended up settling for method #2 - block the entire CSS...
this WILL "break" a lot of sites...
i am generally on a site to READ its content, i don't see the need for SSL connections to "inform" Facebook, Twitter, Tumblr, LinkedIn, etc


so i block the CSS and intentionally "break" the neat and pretty page layout...
might not be for everyone, but if you don't like "3rd Party Shenanigans", this one very simple filter will go a very long way to block them Smile!

Code:
Name = "Block SSL CSS on non-SSL Sites [add]"
Active = TRUE
URL = "$TYPE(htm)$TST(uProt=http:)"
Bounds = "$NEST(<link,>)"
Limit = 512
Match = "\1href="https:\/\/\2.css"\3"
Add Thank You Quote this message in a reply
Feb. 05, 2015, 12:44 PM
Post: #2
RE: "off-site" blockers
(Feb. 05, 2015 12:28 PM)ProxRocks Wrote:  ...so i block the CSS and intentionally "break" the neat and pretty page layout...
might not be for everyone, but if you don't like "3rd Party Shenanigans", this one very simple filter will go a very long way to block them Smile! ...

Thanks Smile! Any particular place in the config that the filter needs to be placed?

soccerfan
Add Thank You Quote this message in a reply
Feb. 05, 2015, 12:54 PM
Post: #3
RE: "off-site" blockers
i place it at the bottom of the "|||||||||||||||||||||||||||||||||||||||||||| Anti-Tracking" section...
Add Thank You Quote this message in a reply
[-] The following 2 users say Thank You to ProxRocks for this post:
soccerfan, defconnect
Feb. 05, 2015, 11:15 PM
Post: #4
RE: "off-site" blockers
URL field updated, functionally still the same, just matches sidki's $TST convention versus the older $TYPE convention -
Code:
Name = "Block SSL CSS on non-SSL Sites [add]"
Active = TRUE
URL = "$TST(hCT=*html)$TST(uProt=http:)"
Bounds = "$NEST(<link,>)"
Limit = 512
Match = "\1href="https:\/\/\2.css"\3"
Add Thank You Quote this message in a reply
Feb. 05, 2015, 11:29 PM
Post: #5
RE: "off-site" blockers
WHAT'S WITH THE NEW [email protected] 403 FORBIDDEN PAGE WHEN TRYING TO POST A COUPLE FILTERS ??? ??? ???
Add Thank You Quote this message in a reply
Feb. 05, 2015, 11:32 PM
Post: #6
RE: "off-site" blockers
two 3rd Party Image filters attached...


JJoe / Kye-U - seriously, what's with the [email protected] 403 Forbidden page ??? ??? ???


Attached File(s)
.txt  filters.txt (Size: 2.34 KB / Downloads: 348)
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: