+- The Un-Official Proxomitron Forum (https://www.prxbx.com/forums)
+-- Forum: Proxomitron Config Sets (/forumdisplay.php?fid=43)
+--- Forum: Sidki (/forumdisplay.php?fid=44)
+--- Thread: eWeek timer loop (/showthread.php?tid=1248)
eWeek timer loop - DarthTrader - Jan. 29, 2009 05:59 PM
eWeek has a timer which I believe is new. It keeps looping and I can't get past it.
TIA,
DarthTrader
RE: eWeek timer loop - sidki3003 - Jan. 29, 2009 06:17 PM
Noticed that too. What worked for me was replacing in IncludeExclude:
Code:
www.eweek.com/ $SET(1=cookie_b:2.)...with:
Code:
www.eweek.com/ $SET(sUserFn=§cookieEnabled§)RE: eWeek timer loop - Graycode - Jan. 29, 2009 07:51 PM
I'm just curious: What is the Proxo code that would remove anything before the !DOCTYPE tag on pages if that tag exists and it's before the HTML tag?
That might be another approach for invalid content such as what's now being generated by eweek.
RE: eWeek timer loop - sidki3003 - Jan. 29, 2009 08:17 PM
The actual code depends on the config. For private configs you can test for the first occurrence of <(!doctype|html|head|body), set a global flag and exit. Then let another filter remove any tag blocks you want, as long as mentioned flag hasn't been set. Once it has been set, let this second filter exit as well.
As for recent public configs, it's already in. However, apparently you can't expect people to write proper HTML. Even major sites often don't care about document structure (one of the worst being Google).
Thus, i've cut back pre-html block removing over the years. Currently pre-html blocks only get removed if they contain 3rd party scripts, iframes, and obvious junk (tables, <center>, etc.).
edit: What i entirely forgot is that you can still do that on a per-site basis, d'oh!
So this is probably the better approach: replacing the old IncludeExclude entry with:
Code:
www.eweek.com/ $SET(0=s_prehtml.)Thanks
