malmazan Posted September 21, 2018 Report Share Posted September 21, 2018 Hi all: Moving to https, it seems only Asynchronous JS invocation works. Regular Javascript (which is what I need) and iframe invocation do not seem to work, with relevant 'http' changed to 'https' and over a plain HTML file. I'm running revive 4.14. PHP is 5.6 (though problem was the same with PHP 5.5), MySQL 5.6, Apache 2.4 Thanks in advance for the help Quote Link to comment Share on other sites More sharing options...
malmazan Posted September 21, 2018 Author Report Share Posted September 21, 2018 I'm using standard invocation codes, only changing http to https where needed Also, although Asynchronous JS invocation does show banners over https, lg.php end up being called from http://, so browsers will not qualify the page as secure Quote Link to comment Share on other sites More sharing options...
malmazan Posted September 22, 2018 Author Report Share Posted September 22, 2018 Tried changing "protocol" (under [origin] in conf.php) from "http" to "https" Ended up locking myself from the control panel ("Due to a problem with the database Revive Adserver couldn't retrieve or store data"), though banners are still being served. Changing "protocol" back to "http" did not help with the CP issue Quote Link to comment Share on other sites More sharing options...
malmazan Posted September 28, 2018 Author Report Share Posted September 28, 2018 I did a new, fresh, test, install of Revive Server. Again, only Asynchronous JS invocation works. Regular Javascript does not. I was able to get lg.php to serve via https. I still do not understand why my working install does not. 'Some Http:' is only used as URL destinations. I even did an Phpadmin search to make 100% sure of this. Any ideas? Quote Link to comment Share on other sites More sharing options...
malmazan Posted October 9, 2018 Author Report Share Posted October 9, 2018 Still trying. I sequentially turned off (via dates) all campaigns and the problem persists. The https page is initially loaded as secure by the browser, but when the Asynchronous JS banners are loaded, it shows it as insecure. (When Javascript is off, the page loads securely alright via https, though) Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted November 6, 2018 Report Share Posted November 6, 2018 I'm pretty sure that AJS, regular JS and iFrame all work just fine with HTTP and HTTPS. Apart from saying it's not working (and one comment about logging via HTTP when the initial call was via HTTPS), there's really not any details in the information above - no examples we can see, no screenshots, no error messages.... Not much I can do to help at this stage as a result! However, maybe try: https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering+over+SSL ? Quote Link to comment Share on other sites More sharing options...
malmazan Posted November 7, 2018 Author Report Share Posted November 7, 2018 On 9/28/2018 at 12:16 PM, malmazan said: On 11/6/2018 at 7:25 AM, andrewatfornax said: I'm pretty sure that AJS, regular JS and iFrame all work just fine with HTTP and HTTPS. Apart from saying it's not working (and one comment about logging via HTTP when the initial call was via HTTPS), there's really not any details in the information above - no examples we can see, no screenshots, no error messages.... Not much I can do to help at this stage as a result! However, maybe try: https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering+over+SSL ? I finally fixed my ads being served unsecurely. I used .htaccess redirects for the altervative "Delivery File Names" and they were redirecting to http pages. That also seems to have fixed the javascript banners not being served at all. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted November 8, 2018 Report Share Posted November 8, 2018 Glad it's fixed for you. You should not normally need to use .htaccess redirects for serving banners over SSL, so if anyone in the future reads this thread, please be aware it should (and normally does) work without this - I suspect there's some other issue going on in this case which hasn't been identified yet. Quote Link to comment Share on other sites More sharing options...
malmazan Posted November 9, 2018 Author Report Share Posted November 9, 2018 If using "Delivery File Names", the files need to be redirected somehow (unless one wants to manually change file names every time one updates Revive), though I guess I could have used a symlink redirect that did not specifically redirect to an "http" URL. Way back then, though, I did not imagine Google will force us to go SSL Ideally, revive could write the symlink rewrites to an .htaccess files Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.