quazardous Posted May 13, 2014 Report Posted May 13, 2014 hi, what can be safely put in a varnish or a cdn ? the image url (http://www.domain.com/www/images/cnczcozcoz.gif) ? other ? Quote
Snoork Hosting Posted May 23, 2014 Report Posted May 23, 2014 Go for Nginx with mix of Apache. Your costs for use of CDN may run high if you will start serving millions of impressions per day. Quote
techs Posted May 28, 2014 Report Posted May 28, 2014 Simply Setup an Nginx proxy with your apache , if your site is not so big . Quote
alexus Posted June 2, 2014 Report Posted June 2, 2014 We're experiencing an issue with OpenX 2.X and Varnish 3.x. Whenever an OpenX Admin tries to navigate through the backend interface by clicking on any link, OpenX shows the login page. For example, an admin logs into the backend and after clicking on the "My Account" link, he will see the login page again. After logging in a second time, he will see the "My Account" page. The one thing we've noticed is the sessionID seems to change every request. We have OpenX installed on two backends with a Varnish proxy (version 3.x) in front. We have a Varnish's director `client` to load balance between the two backends. Varnish': director app02 client { { .backend = app02a; .weight = 1; } { .backend = app02b; .weight = 1; } } vcl_recv(){ ... set client.identity = req.http.cookie; ... } Please advise. Quote
andrewatfornax Posted June 3, 2014 Report Posted June 3, 2014 Does this also happen with Revive Adserver? Quote
alexus Posted June 4, 2014 Report Posted June 4, 2014 Does this also happen with Revive Adserver? As of now we're still using older version of OpenX (2.8.x), however if you're know for a fact this should not be happening with newer version of OpenX (Revive), I'll make an effort to upgrade it to latest and greatest) ASAP). Do you know if new OpenX stores session inside of database? So that another web head can pick up wherever the other one left off? Quote
alexus Posted June 6, 2014 Report Posted June 6, 2014 I'm trying out revive-adserver-3.0.5 and I keep getting following message: You need to enable cookies before you can use Revive Adserver - DISABLED I've tried with several browsers: Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Internet Explorer... Configuration of your webserver does not meet the requirements of the Revive Adserver. In order to proceed with installation, please fix all errors. For help, please see our documentation and FAQs documentation link is http://documentation.revive-adserver.com/ FAQs link is http://documentation.revive-adserver.com/faq Quote
andrewatfornax Posted June 8, 2014 Report Posted June 8, 2014 As of now we're still using older version of OpenX (2.8.x), however if you're know for a fact this should not be happening with newer version of OpenX (Revive), I'll make an effort to upgrade it to latest and greatest) ASAP). Do you know if new OpenX stores session inside of database? So that another web head can pick up wherever the other one left off? No, unfortunately, I don't know if Revive Adserver works with Varnish - not something I have tried yet. Revive Adserver definitely works fine with multiple web servers, though. I'm trying out revive-adserver-3.0.5 and I keep getting following message: You need to enable cookies before you can use Revive Adserver - DISABLED It looks like for some reason, Revive Adserver thinks that cookies are not able to be set. Are you able to confirm that cookies are being set by the domain that you're installing Revive Adserver on, in the browser you're using? Quote
mateomiguel Posted January 26, 2015 Report Posted January 26, 2015 Revive ad server can't be run from behind varnish. You will have to configure varnish to ignore the subdirectory that you put revive ad server in. Do this by adding the revive ad server subdirectory to the list of directories to ignore in varnish's config, default.vcl, like this example: if (req.url ~ "^.*/revive-ads/.*$") return (pass); Quote
mateomiguel Posted January 26, 2015 Report Posted January 26, 2015 Revive ad server can't be run from behind varnish. You will have to configure varnish to ignore the subdirectory that you put revive ad server in. Do this by adding the revive ad server subdirectory to the list of directories to ignore in varnish's config, default.vcl, like this example: if (req.url ~ "^.*/revive-ads/.*$") return (pass); Quote
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.