Giorgio Maone wrote:Restored Surrogates functionality in latest development build 2.4.5rc3 (you can forbid google-analytics.com again, now).
Tom T. wrote:Please refresh my memory on the order of processing between NS and RP, sorry.
Giorgio Maone wrote:Tom T. wrote:Please refresh my memory on the order of processing between NS and RP, sorry.
By default, NS comes always the last: this was introduced years ago to allow ABP users to see stuff blocked later by NoScript among ABP's "Blockable objects".
This is controlled by the noscript.cp.last about:config preference: if you turn it to false, content policy execution order will depend on component registration order, which isn't always obvious.
Tom T. wrote:Confirming that I understand correctly: In the default configuration, I must TA or allow in RequestPolicy requests to G-A, so that RP will allow this to get to where NS sees it, whereupon NS runs the surrogate. Correct?
And the Hosts blocking is irrelevant to the above, because the original request is internally processed through RP to NS, which runs the locally-stored surrogate, thus never triggering a (Hosts or DNS) lookup to G-A. Correct?
If I have that right, then I understand the need to allow G-A in RP.
Users browsing this forum: No registered users and 1 guest