RequestPolicy/requestpolicy — Issue #276: Urls  redirected to ISP Server Cache
Author: jsamuel
Created: 2011-12-22 19:03:49+00:00
State: open
Labels: extension

imported trac ticket
created: 2011-10-27 04:54:04
reporter: zozo

I have recently been encountering blocked urls like this one, likely inaccessible to you:

http://1.1.1.4/bmi/www.engadget.com/media/linkarea_siteswelike_sm.gif

and this:

http://1.1.1.3/bmi/www.huffingtonpost.com/favicon.ico

and this last one,

http://1.1.1.1/bmi/g-ecx.images-amazon.com/images/G/01/askville/elements/bs-loader._V01_.gif

which is on this interesting page that you should please read:

http://askville.amazon.com/SimilarQuestions.do?req=url+path+bmi

The askville page explains what I think the problem is.

How can requestpolicy work around it?

The problem is that a page might contain links to two images from different origins both of which reside in the same server cache directory, one wanted, the other not. eg.

http://1.1.1.2/bmi/www.abc.com/goodimage.jpg

http://1.1.1.2/bmi/www.xyz.com/badimage.jpg

In this example, a policy applied to 1.1.1.2 will not have the desired effect.