[pseudonym]

Originally Posted by davews

Much has been suggested about the https:// cookie. But in fact this will only work for those sites where all the code on that site is secure, ie an https://site (and which Phorm is unable to profile even if it tries). Just having a single https:// image will mean that site has mixed secure and unsecure content and most browsers will flag this up with a weak security popup error which will alert the user to something not quite right going on. So it is broadly unviable.

Fair point, opening a https page from within the http page using javascript or just redirecting the http: page request to a https: page would avoid that problem.