Filter not working on some web pages

[Oddysey]

(Dec. 13, 2008 09:49 PM)Kye-U Wrote:  

Code:

[HTTP headers]
In = FALSE
Out = TRUE
Key = "User-Agent: Spoof Intuit - IE6 on Windows XP (out) "
URL = "(\w.|)intuit.com"
Replace = "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"

One note here, on the URL Match line.....

I don't know for sure, I'm not an Intuit user, but it seems to me that this might be a "secure" page, with an HTTPS protocol, not the normal HTTP. Even so, it sometimes happens that, and I've fallen for this myself (with JJoe bailing me out!), you'll see the HTTP protocol, but it's being routed through Port 443 - that's the "secure" communications port, or so they say. In order to make sure that all your bases are covered, you should probably write that line like so:

URL = "(\w.|)intuit.com\w/"

You also want the trailing slash, as Scott explains in his Help file, to make sure that all subsequent pages from that domain are also filtered.




My take on bluechalk's problematic solution is that Proxo can and will change code, even script code, if it's written directly within the page contents. However, if a script is called from an external source, then it won't be modified, unless the filter URL Match specifically calls for a $TYPE(js). As ProxRocks points out, sidki3003 does do just that in his config set.

Might give that some thought......


BTW, welcome to the Forums, bluechalk!


HTH



Oddysey