static.ak.facebook.com

[scoop]

Can anyone help me with this problem. Every so often when visiting web pages I get this pop up at the bottom of my browser
When you open the script in note pad all it says is /* PROX: HTML Content Killed */
I havent changed anything with the filter set.

[JJoe]

No but then I don't use facebook and I have a Exceptions-U entry that looks like

Code:

[^/]++.facebook.com/ $OHDR(referer:?&(^https+://[^/]++facebook.[^./]+/*))$RDIR(http://local.ptron/killed.gif)

The idea being requests to "*.facebook.com" from pages that are not "*.facebook.com" are not allowed.

Are you using facebook when you see these messages?

[scoop]

(May. 11, 2014 08:05 PM)JJoe Wrote:  Are you using facebook when you see these messages?

No it doesn't happen on Facebook, just all other sites strangely enough. If I bypass Proxomitron and reload the page it goes away but reappears after a few days. The only thing I can think of is the Facebook like button is having problems with my setup.

[JJoe]

Facebook wants to know what we are all doing. So, the web is littered with requests for various facebook files. From the referer on the request or the request's url or other data, facebook gets some idea of what we are doing.

Try adding the posted entry to Exceptions-U.

If you should need the blocked file, we will have to do something else.
Note the address of the page when you see the dialog.

HTH

[scoop]

Tried what you suggested, cleaned cache etc too but still doing it. Ive included a couple of sites
http://www.digitalspy.co.uk/cult/#~oE2TA47sXqFE5N

http://www.dailymail.co.uk/mailonsunday/index.html

[ProxRocks]

if you enable the header filter "7.1 Block all Scripts", then not only are these facebook sort of things blocked, but you also don't have to tinker with your Proxo config on a DAILY basis to track down these sort of things...

then when web sites absolutely positively "need" all of the CRAP that comes with scripts, then in THREE mouse clicks and about a second and a half, you access the "allow scripts" from sidki's lower corner menu...



ps - "jab" aside, i looked for static.ak in the source code of those two web pages and did not see it, maybe it's a geolocation thing and US IP's are served different code...

[JJoe]

(May. 12, 2014 11:30 AM)scoop Wrote:  Tried what you suggested, cleaned cache etc too but still doing it. Ive included a couple of sites
http://www.digitalspy.co.uk/cult/#~oE2TA47sXqFE5N

http://www.dailymail.co.uk/mailonsunday/index.html

I have IE11 but don't see the dialog for the file there. I have found the code for the file in a script from facebook.net, however.

So what happens after you also add

Code:

[^/]++.facebook.net/ $OHDR(referer:?&(^https+://[^/]++facebook.[^./]+/*))$RDIR(http://local.ptron/killed.gif)

to Exceptions-U?

BTW this security feature seems to be unique to IE.

[ProxRocks]

my initial thought was that it was an incorrect mime type, but i couldn't get to the dialog either...

[JJoe]

(May. 13, 2014 02:44 AM)ProxRocks Wrote:  my initial thought was that it was an incorrect mime type, but i couldn't get to the dialog either...

Was mine too. Oddly, one of the 'solutions' I read about was to use an incorrect text/html mime.

I may see it when loading a script in an iframe or window or tab with IE. Using the cfg's menu's "Show ?? Scripts" usually generates a few, which ended the IE experiment years ago.

I ticked and unticked to no avail.

[scoop]

A through clear out tracking protection and activex filtering in IE11 and the code added to exceptions-u seems to have done the trick, many thanks again guys.

Your continued support and help is superb.