Msg#: 4240905 posted 9:56 am on Dec 10, 2010 (gmt 0)
I've built a site in which every page is served via https. I'm getting tired of going through an entire sign up process with networks only to discover that they won't serve their content via https as well. (AdSense). Can anyone offer any suggestions?
Msg#: 4240905 posted 11:38 pm on Dec 10, 2010 (gmt 0)
> Is there a particular reason why every page needs https?
It's a research site, and the research topics may be personal.
> I dont yhink it would help if any did, since a site running ssl can only be bound to one endpoint.
In my experience, it makes a big difference: a web page served over SSL can have media from many different servers in it. Each media item simply also needs to be served via SSL. Google analytics will do this, for example.
Msg#: 4240905 posted 2:04 pm on Dec 14, 2010 (gmt 0)
AdSense is available as https
That is annoying. Sure would be nice if the ad networks had a quick FAQ to find out if they offer their feed on SSL, before you sign up.
OTOH, if an ad network offers their feed as a raw XML web service (or something like that), you can write a proxy script that requests the ads, then serves them from your own domain on SSL. YPN used to work that way, as did Overture.
But if the ad network merely works via a drop-in <script> (many do) and the @src isn't available on SSL, then that won't work. :(