Hello,
For a long time I've found that disabling this filter (below) allows me to see the Google Search 'cached header' at the top of the page. ( ie I like to see it when looking at the cached page)
Is there a way to change this filter so that I can turn it back on and still be able to see the cached header?
I'm asking as I don't know what this filter actually does, so maybe my turning it off is undesirable for some other reasons?
Thanks a lot for any expert help,
Lee
Code:
Filter name
Remove: Specific Pre-Head Blocks 7.07.02 [sd] (d.2)
URL match
$TYPE(htm)(^$TST(keyword=*.(a_ads|a_prehtml).*))
Search and replace
Matching expression
<(
$TST(tHead=*)$STOP()PrxFail$TST()
|$TST(mHtml=[#1:*]$SET(1=head)|h-ta(g)\0$SET(1=html))(^$TST(comment=1))
(
script$TST(\0=*)[^>]++src=$AV(([^/.]+//)\3(^([^/]++.|)$TST(uDom)(^.))\4)$INEST(<script,</script)
</(script)\2*>( <noscript*</noscript >)+$SET(script=)
|(^$TST(script=*))(
center$INEST(<center,(^*<(!doctype|html|head|body))*,</center)</(center)\2 >
|table$INEST(<table,(^*<(!doctype|html|head|body))*,</table)</(table)\2 >$SET(tTable=0)
|div$INEST(<div,(^*<(!doctype|html|head|body))*,</div)</(div)\2 >
|(iframe)\2*>(*</iframe >|)($TST(tIframe=1)$SET(tIframe=)|)
|a\s[^>]++href=*(</a >|>(^(^ <(html|head|body))))$SET(2=a)$SET(tAnc=)
)
)
$SET(eCode=$GET(eCode)
%3Cspan class=%22ProxFly-Span%22>pre-\1:%3C/span> \2%3Cbr class=%22ProxFly-Br%22 />)
($TST(volat=*.log:2*)$ADDLST(Log-Main,[$DTM(d T)]\tWEB Strip_Pre_\1 \t\2 \t\u)|)
)(<\?xml*\?> )+(<!doctype *> )+
Add the following line in your IncludeExclude-U list, under section 2.11, "
allow unexpected pre-html/head/body code $SET(0=a_prehtml.)":
Code:
209.85.173.104/search\?q=cache: $SET(0=a_prehtml.)
I'm not sure if the IP Address is the same for all cache pages; you may have to modify it if you come across any cache pages that have the pre-HTML code removed.
Let me know if you need further instructions on how to locate and modify the IncludeExclude-U list
Great, thanks a lot, Kye-U.
I search on google dot co dot uk and the cache IP always (so far) seems to be 66.102.9.104
With that as the IP in your line, and the filter itself turned back on, indeed I'm seeing the cached header.
Thanks very much! Very clever !
Lee
PS Here's how my Include / Exclude U list looks now ; I assume it's right ...
Code:
## ============================================================================
## 2.11 OTHER
## ============================================================================
[big snip here, and only here, not in the list itself]
----------------------------------------------------------------------------
## don't add Proxomitron menu $SET(0=a_nomenu.)
## ----------------------------------------------------------------------------
## allow unexpected pre-html/head/body code $SET(0=a_prehtml.)
66.102.9.104/search\?q=cache: $SET(0=a_prehtml.)
## ----------------------------------------------------------------------------
## allow unexpected post-html code $SET(0=a_posthtml.)
## -------------------------------------------------------------------------
[big snip here, the list continues]
Hello again,
I'm now finding other ip addresses are coming into play on the google cache.
I'm assuming this could become an arduous drip drip drip of many ip addresses, so I've looked up the ip ranges for 3 ip addresses I've seen so far, using whois-search dot com
They are :-
64.233.160.0 - 64.233.191.255
66.102.0.0 - 66.102.15.255
216.239.32.0 - 216.239.63.255
It is possible to get your code accommodating all the above?
If so, presumably I'd be allowing quite a lot of Google to bypass the filter 'Anti-Ad II - Generic Remove: Specific Pre-head Blocks'? (and potentially more if I find more ip ranges come into the equation)
Is this likely to break / counteract other Anti-Ad or Anti-Google filters in the config?
If yes, maybe this isn't such a good idea just to get the cached header.
??? !
Thanks again,
Lee
Code:
(64.233.[#160:191]|66.102.[#0:15]|216.239.[#32:63]).[#0:255]/search\?q=cache: $SET(0=a_prehtml.)
This shouldn't affect any of the other filters as it refers to the IP Addresses, not the Google.--- domains
Great, thanks very much again. I'm most grateful.
I'll try that out.
If any other ips are needed I'll hopefully now be able to work out myself how to add them too.
Lee