Welcome to WebmasterWorld Guest from 188.8.131.52
Way back when (6 or more months) we used some of the techniques posted in those discussions for one of our online stores and thought we had everything "clean" and had kept G from reaching our https: pages.
However, we neglected to spot some absolute https: refs being used for button images in a left navigation panel which appears for every http: page in the online store. This came to light last week and we changed them to relative references resolving to an http: image.
Now for the question.. (w.r.t. Google) has any of the "https-ness" rubbed off onto:
the link associated with the image,
to the page where the images were located or
to the SITE?
The reason I ask is that prior to this, even though we thought we had everything "clean", one could, on occasion, a site:domain.com and get [domain.com...] as the first entry.
I know a rewrite rule or some way of doing a re-direct would probably have been best, but the storefront software generates the actual references from a config file and we have no way of making changes to the code.
What I'm curious about is how Google treats an http: page with https: image references in the context described above.