Jump to content
mash33

Moving Revive Adserver to SSL (HTTPS)

Recommended Posts

Hi,

We are in the process of moving our site to SSL. In order for our site so comply with SSL, all content served in our site also has to be loaded over https. This includes ads served by our hosted Revive Adserver.

I've had a look around and haven't been able to find a clear guide on how to move Revive Adserver to https.

We'd like to change the entire adserver domain to https, including the ad serving. We mostly use iFrames.

Anyone who has done this before and could provide some assistance?

Thanks.

Share this post


Link to post
Share on other sites

Nothing needs to be done to Revive Adserver itself. It's a webserver configuration issue.

If the current invocation code of your existing zones specifically points to http://... just configure the web server that runs your ad server to work over https, and then change the invocation code from http://... to https:///

If your banners happen to refer to externally hosted images that are entered with http:// you will have to update those as well.

Share this post


Link to post
Share on other sites

Hi Erik,

Thank you for the quick reply and assistance.

If the webserver is set up correctly to run over https, will Revive Adserver automatically generate new invocation codes to https:// ?

I know I'll have to manually change all the old invocation codes from http:// to https://

Thanks.

Edited by mash33

Share this post


Link to post
Share on other sites

The javascript invocation code automatically switches from http to https if it runs on a webpage that's also https (that includes any javascript invocation code you already have on your pages).

And I think when you access the Revive Adserver UI over https and have it configured correctly, new iframe invocation code will be generated for https.

Edited by Erik Geurts
typo

Share this post


Link to post
Share on other sites
On 19/09/2016 at 11:05 AM, Erik Geurts said:

The javascript invocation code automatically switches from http to https if it runs on a webpage that's also https (that includes any javascript invocation code you already have on your pages).

And I think when you access the Revive Adserver UI over https and have it configured correctly, new iframe invocation code will be generated for https.

I tried that and it did not work. Still creating invocation codes with http:// on them.

Is there a place on the database where I could search/replace to fix that?

Share this post


Link to post
Share on other sites
29 minutes ago, femdom said:

Any solution to your problem, I am about to do the same

We moved over to https without issues. I forced https across out entire ad server using .htaccess which worked, but I still had to update all iframe invocation codes to https. Generally, there are 3 references to http resources per invocation code. After the https migration, new invocation codes were still being generated for http, so we still have to manually change the links to https. If you use JavaScript invocation codes, https works automatically.

Edited by mash33

Share this post


Link to post
Share on other sites
8 minutes ago, femdom said:

Ok thank you. I've just told my hosting to do it. They told me this ( so is it ok to do it this way?):

we suggest enabling https without forced redirection to https

Yes, you can also do this, although you might not get the full advantage of https. As your host suggests, enable https without forcing it as a start. Then log into your account using the https version of your site (as both http and https will be available) and test if everything works fine. Once you are happy that there are no problems, I suggest forcing https with htaccess.

Share this post


Link to post
Share on other sites

OK, we did it but an unexpected problem just occurred. Actually, all is working except that admin area looks ruined when accessed with https. With HTTP it is ok. Look at the print screen please : https://prnt.sc/iqs3lh Guys from hosting are confused, so they told me to ask next:

I suggest that developers clarify the recommendations for setting up the "revive adserver" to work with the software nginx (frontend) + apache (backend) + php-fpm

Perhaps we are missing some small, but very important setting.

P.S. in the documentation on their site I did not find the technical description, only general settings

Share this post


Link to post
Share on other sites

I think there is another topic going on at the moment with this same issue, that HTTPS access to the admin UI doesn't work (assets missing). Try turning on the UI option to enforce HTTPS access only (the "requireSSL" option of the config file) and see if that fixes it?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




×
×
  • Create New...