Re: privoxy conundrum [*NOT* solved]

[Patrick Mansfield <patman aracnet com>]

On Mon, Oct 12, 2009 at 01:59:31PM -0600, Petrus de Calguarium wrote:
> This is not solved, after all.
> 
> Perhaps you *do* have to service privoxy restart and 
> restart the browser. All was working splendidly, now it 
> hangs on google-analytics again, just like before.
> 
> google-analytics is dealt with in the default.action 
> file, but clearly this doesn't work correctly.
> 
> Any more ideas?

I put ssl.google-analytics.com in the privoxy user.action file, under the 
"{ -block }" section.

I also used ghostery's blocking in firefox, then I could it in ghostery,
and the page still loads.

Yesterday, I was playing with it some - sometimes privoxy blocks (and logs
the blocking) of the requests, sometimes it does not, I'm not sure why. I
cleared the cache and cookies (in firefox), but no change. And, then the
page loaded fine with ssl.google-analytics.com blocked.

And, today the page won't load :-(

I get this logged:

	Oct 16 13:36:28.496 Privoxy(b73ffb70) Request: ssl.google-analytics.com:443/ crunch! (Blocked)

The really sad part is that this is my *bank*! I complained, but they
haven't changed anything, I think they need to be publicly shamed.

-- Patrick Mansfield