Before I'm using Cloudflare, the Google ads still showed up, but it won't show now. Here's my site http://blog.andra.systems/ (There's should be Google ads on the sidebar). I've tried to remove cache and cookie, also I'm trying with web capture service and no sign of Google ads.
Note: I've turned off DNS and HTTP Proxy, auto minify and rocket loader.
Edit:
The ads strangly appear now
Make sure you are not mixing HTTP content with https.
Example using HTTP Adsense code in a secure SSL enabled website with https address.
if you are making that mistake then change the HTTP code with https that would solve the problem.
Related
I'm putting analytics on a facebook application and i'm unsure what the protocol would be.
Here's a screenshot from the analytics set up
In general I would prefer https. No idea what google does with it but https is the best way to share your application and its contents. If you run your App in a facebook iframe tab your app has to be reachable via https. That means that the content also gets shared via https (because FB will call your app by the users privacy settings (http or https)).
So all my apps and their sharing URLs are set to https so that the like-count etc. are the same and are reachable whether called via FB or not. Because of this I would prefer the https way.
Facebook now requires https for all applications, so I don't see any reason not to use https for your analytics script.
However, if you use a protocol-less url, your browser will figure out for you. E.g.
<script type='text/javascript' src='//www.google.com/yourscript.js'></script>
No problems with making our webserver secure. App on Facebook runs fine IF 'secure browsing' opted in (user-setting). How can we make our App visible for visitors who has not opted in on 'secure browsing'?
Do we have to make a copy of the site on a insecure (http) server? Or is there another solution? (force to non-ssl via htaccess)
There should be no issue with setting both app urls, in your Facebook app settings, to use the https url.
I'm using a self generated SSL certificate on my localhost IIS and pointed my facebook sercure Iframe app URL to https:\localhost but just get a blank page.
when browsing to it not within FB, it gives me the cert warning and then after i add it as an exception, it goes through to the site fine.
using http:\localhost for the non-secure url works fine
any ideas why i'm getting the blank page?
As I know FB checks your certificate and if it not valid it just wont load your app in the iframe. You can try this service that seams to be intended to exactly this kind of problems: http://www.social-server.com/.
Don't stress if you can't afford an SSL certificate for Facebook's SSL migration...
...Use this FREE service to adapt your Facebook pages so that it's viewable over an HTTPS connection.
Facebook and their app partners seem to achieve this.
If you look at the Farmville URL you can see it's serving over SSL: https://apps.facebook.com/onthefarm/?ref=ts
Facebook then iframe in the content from the game provider (Zynga) using another SSL iframe src. But then you see ad code called via non-secure external JS calls.
What are the rules/techniques concerning delivery of non secure page elements (Flash, images etc) without mixed content warnings in iframes when the top level page is serving over SSL?
SSL Page (Facebook) > SSL iFrame (App Provider) > Non-SSL iFrame (App Provider) > HTTP image/Script call?
You can't really use a custom app page without using SSL. But if you are looking for a free alternative you can use facebook app provides like http://devcenter.heroku.com/articles/facebook
You can even use dropbox as an free alternative if you wanna host your iFrame fan page.
For a paid and best solution, you would need an web hosting and a domain with dedicated IP and SSL installed on it.
We're developing locally a facebook app that should reside in a page tab.
The app is in sandbox mode, so the secure url should not be required - still, the "please update your secure url" message appears.
All work perfectly on the non-tab ("Apps on facebook.com") version, so I'm pretty sure it's a bug/"undocumented feature" and I'm probably gonna get my local apache version to accept secure requests - still, I'd like to know if anyone can figure out something I'm missing.
Thanks.
You could disable HTTPS on your account while testing? The behaviour before that message was introduced was that the tab wouldn't render link at all if it didn't support HTTPS but you were browsing in HTTPS mode