Jump to content

tobean

Approved members
 View Profile  See their activity

  • Posts

    36

  • Joined

  • Last visited

 Content Type 

Posts posted by tobean

  2. Google PageSpeed Insights problem

    in Performance, Scalability, and Reliability

    Posted

    The tool told me to use browser caching for /www/delivery/asyncjs.php (60 minutes)

    I added the following code to my .htaccess file and Page Speed Insights is happy and gives me a higher score:

    <Directory "/www/delivery/asyncjs.php">
    <Files "asyncjs.php">
    ExpiresActive on
    ExpiresDefault "now plus 1 hour"
    </Files>
    </Directory>

    But with this optimization I don't see any banners ... If I remove it I see the banners but Page Speed Insights told me to use browser caching.

    What's the mistake or is it not possible to use browser caching for the file asyncjs.php?

    Best regards

    tobean

  3. 2 problems with https version of revive adserver

    in Managing Revive Adserver

    Posted

    Thank you, Eric.

    Indeed, ad requests from Google Adsense are https and others start with https://www.adserver.de/adserver/www/delivery/ck.php?oaparams=2__bannerid=192__zoneid=39__cb=6682877f85__oadest=http%3A%2F%2Fwww. ...

    The logout problem seems to be a misconfiguartion in my .htaccess file!

    Last question: Why do I see no banners with the following configuration in my .htaccess?

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

    It should change any http request to https on our adserver.

    tobean

  4. 2 problems with https version of revive adserver

    in Managing Revive Adserver

    Posted

    Hi Eric,

    thank you but why will I be forwared from a https page to a http page when I try to log out?

     

    (link https://www.adserver.de/adserver/www/admin/logout.php forwards me to http://www.adserver.de/adserver/www/admin/ )

    And I guess that banner delivery is https with "requireSSL=1" because the banner links change to https://www.adserver.de/adserver/www/delivery/ck.php?oaparams=2__bannerid=192__zoneid=39__cb=6682877f85__oadest=http%3A%2F%2Fwww. ...

    What must I do to change everything to https ?

    tobean

  5. 2 problems with https version of revive adserver

    in Managing Revive Adserver

    Posted

    I have changed the configuration to SSL by changing the flag "requireSSL=1" in the config file and everything works fine. In addition I've installed password protection for the directory "www/admin".

    When I try to logout in the backend I'll be forwarded to the http-verson "of www/admin/" (correct would be the https-version). Therfore I have to put in my .htaccess password again every time I log out from the backend. Is this a bug or should I change another flag in the config file or somewhere else?

    The second problem:  When I force every http reqest to be https with the following commands in the .htaccess file no banners will be displayed. What is the mistake? The configuration works fine some other domains on my server without banners from my revive ad server:

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

    Thanks for every help.

     

  7. Version 4 still does not run with PHP7?

    in Managing Revive Adserver

    Posted

    Hi!

    I've just upgraded from 3.2.4 to 4.0.0 without any problems (php 5.6, https). Then I tried to switch to PHP7 and still got an empty screen on the login page and the following error messages:

    Has anyone an idea or is this still a bug in 4.0.0?

    [30-Sep-2016 08:04:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function dl() in ***/adserver/lib/pear/PEAR.php:758
    Stack trace:
    #0 ***/adserver/lib/pear/MDB2/Driver/mysql.php(400): PEAR->loadExtension('mysql')
    #1 ***/adserver/lib/OA/DB.php(196): MDB2_Driver_mysql->connect()
    #2 ***/adserver/www/admin/config.php(24): OA_DB::singleton()
    #3 */adserver/www/admin/index.php(17): require_once('/usr/www/users/...')
    #4 {main} thrown in ***/adserver/lib/pear/PEAR.php on line 758

    Tobean

  11. Upgrade To 3.1.0 Not Possible - Directories Must Be Writable

    in Managing Revive Adserver

    Posted

    Hi!

     

    I tried to upgrade from 3.0.5 to 3.1.0. My system configuarion is: Apache, PHP 5.4.35, MySQL 5.1.73-1+deb6u1.

     

    On the system check page I get 4 error messages that directories are not writable (var, var/cache, var/plugins and plugins). Some other directories have the sampe permissions (777) and the system says it's OK (e.g. www/admin/plugins)

     

    I checked it serveral times but these directories are definitely 777. I have also changed all directories and sub directories to 777 but nothing changes. I used chmod 777 with telnet login.

     

    I have a similar error message in my 3.0.5 installation but everything worked fine (no problems): "Error: File permission errors detected. These may impact the accurate delivery of your ads, See the debug.log file for the list of unwritable files."

     

    What's the problem? Is it possible to deactivate this test in the system check page of the installation procedure? Has anybody an idea or solved this problem?

     

    Thanks in advance for all tips!

     

    Tobean

     

     

×
×
  • Create New...