For one thing, apache 2.4 which loads of people have, doesn't support itquestion is why not use SPDY SSL
Hello , How can redirect all request to https ?You still need to redirect all request to https version.
And that is still 301 redirect as far as I understand.
Let's see.. a tutorial usingA tutorial on how to install and run SSL on xenforo would have been useful i think.
It's configured on server side, not xenforo. The only "xenforo thing" to change is .htaccess files (I consider .htaccess files is server side, not xenforo/cms side)A tutorial on how to install and run SSL on xenforo would have been useful i think.
If you are calling it using the http in your ad template, then change it to // (no http or https) and see if that works.I just bought PositiveSSL and after installing it on my forum, I realised my Ads were not being served. I use BeaconAds.com to serve ads. The Ads script were blocked and shown as unsecure.
If you are calling it using the http in your ad template, then change it to // (no http or https) and see if that works.
That's unusual that it wouldn't... their site itself appears to be SSL so one would assume their ad server would also.Tried it all. Didn't work. I think I might slowly move to Adsense instead. BeaconAds generated better income for my website.
That's unusual that it wouldn't... their site itself appears to be SSL so one would assume their ad server would also.
Hello , How can redirect all request to https ?
nginx?
Apache?
LiteSpeed?
OpenLiteSpeed?
IIS?
Lighttpd?
Cherokee?
Yes, that's what I thought. I contacted the support team and they told me that they do not support SSL at this time and that they are planning to include this feature at the beginning of next year. Their parent company BuySellAds.com support Ads over SSL only for their PRO plan customers only and it cost $500/month to join the PRO plan. Should I go back to Adsense?? Throught Adsense I can only earn half of what I get now through BeaconAds. Tough decision.
Some important things to know about the SSL-compatible ad code:
- The SSL-compatible ad code is designed for publishers who already have existing HTTPS-enabled sites. We don’t recommend that publishers with HTTP sites convert their sites to HTTPS unless they have a strong reason to do so. Unless you're a publisher who needs to protect important user information like credit card details, passwords, or medical records etc., you probably don't need change your site to HTTPS.
- HTTPS-enabled sites require that all content on the page, including the ads, be SSL-compliant. As such, AdSense will remove all non-SSL compliant ads from competing in the auction on these pages. If you do decide to convert your HTTP site to HTTPS, please be aware that because we remove non-SSL compliant ads from the auction, thereby reducing auction pressure, ads on your HTTPS pages might earn less than those on your HTTP pages.
Funny actually that this is technically also from Google on the very same subject, just another department. I guess maybe they didnt get the memo?
Which is hugely ironic considering what happened recently.Eventually users are not going to want to connect to sites that are not secure
Agreed... but the talking mouthpieces will be encouraging encryption. Me, I just really do it because of SPDY and the fact I wanted to try it out (something new to do).Which is hugely ironic considering what happened recently.
We use essential cookies to make this site work, and optional cookies to enhance your experience.