3 ms·
> 1) Embed the images in iframes, which are then embedded in the page. The iframes will swallow the referrer, so provided they are hosted somewhere where logs a
by est 17y ago
> 1) Embed the images in iframes, which are then embedded in the page. The iframes will swallow the referrer, so provided they are hosted somewhere where logs are discarded then it should be fine (I'd want to cross-browser test this before relying on it though).
https will swallow referer automatically.
- nl 16y agoWhich is why I said "..HTTPS is a good idea". There are valid reasons why serving everything under HTTPS isn't always a good idea. The obvious one is CPU cost, but cache performance can also be affected. See, for example: http://blogs.msdn.com/ieinternals/archive/2010/04/21/Internet-Explorer-May-Bypass-Cache-for-Cross-Domain-HTTPS-Content.aspx http://blogs.msdn.com/ieinternals/archive/2010/04/21/Interne... http://blog.pluron.com/2008/07/why-you-should.html http://blog.pluron.com/2008/07/why-you-should.html (I'm not saying that https isn't the best option. I'm just pointing out other options that can work with plain http.)