varnish

Greetings fellow Drupalers!

Despite my best effors i just noticed that some images are not served through the reverse proxy. Those rebellious image files are originating from inside CSS.

This can be easily fixed by making all those images paths absolute.

Does anyone know of a smarter way to fix this, preferably with a generic solution and end this mutiny once and for all?

I stumbled across this article which describes a useful technique for doing cache invalidation. This could work nicely and have many advantages over calculating the list of URLs to invalidate on the Drupal side, as the current combination of Varnish+Expire modules does. We could hook into entity CRUD functions and add headers to the response.

Saludos. Tengo un sitio con drupal y un colage de Varnish y Memcached. Recientemente mi server sufrió varias caídas y según mi proveedor todo indica que la culpa fue del bot de MSN (MsnBot). Temporalmente bloquee BOTMsn por robots.txt. Paralelamente puse la opción Cache en views adicionalmente. Mi duda es si no hay alguna opción para controlar el ingreso del BotMsn sin anularlo del todo y si en algo me ayuda a la carga el poner cache adicional para views. Mi servidor tiene 2gb de RAM.

Saludos y espero algunas sugerencias

Saludos amigos, instalé Varnish en un sitio web con Drupal 7 y tengo algunas dudas y problemillas:

1- Además de Varnish el sitio tiene Memcached corriendo, mi duda es si se disminuye el rendimiento si desinstalo (Memcached). Leí que Memcached utiliza memoria del server y yo tengo sólo 2GB de RAM, entonces me vendría a bien un ahorro.

Saludos amigos..

Hace poco instalé Varnish en un sitio web, todo funcionó correctamente, pero el detalle es que ahora statics (estadísticas) no contabiliza fielmente las visitas a cada nodo. Por ejemplo, si antes tenía 100 visitas en una hora ahora se reduce a 20. Tengo el cache activado por Varnish en settings.php a 15 minutos. Espero alguna ayuda

gracias

Hello everybody

I'm new to Balkan group. I have one question regarding optimizing site with Varnish. I have installed varnish and Expire modules and setup them. They are working very well but I have one problem regarding deleting cache from varnish.

The problem is how to delete varnish cache only for index(home) page and not to delete cache for other pages. I look at he varnish log and I found that whole varnish cache is deleted every time Drupal executes command

ban req.http.host ~ www.cdm.me && req.url ~ "/"

This command is executed by varnish module or expire module.

in our environment even though we have varnish (frontend) w/ apache (backend) somehow logged-in users are able to bring apache to it's knees, it probably have something to do with following:

    // do not serve cached pages for logged in users
    if (req.http.Cookie ~ "SESS[a-f|0-9]+") {
            return (pass);
    }

so I was thinking if it's possible to do following:

1. have pressflow to give out different cookie to a user based on their role.

I've gotten Varnish working in front of Drupal 7. I've also got Pound in front of Varnish, and can successfully browse the site via HTTPS. However, whenever I try to log in over HTTPS, I get a 403 forbidden error, and I'm not entirely sure why. My guess is Varnish-related... but I'm not positive.

Anyone have any ideas/pointers as to what I'm missing? I'm glad to post Firebug output showing the POST to /user and the resulting 403 if it helps.

Relevant snippets from settings.php:
<?php
$conf['reverse_proxy'] = TRUE;
$conf['page_cache_invoke_hooks'] = false;
$conf['cache'] = 1;

I have been tasked with building a block of recently popular content for a site which will get a decent enough level of traffic.

I have a site that has both a large anonymous-use and logged-in participant usage. In an older version, the client used Secure Pages to get some pages into SSL, but to force most traffic back into regular HTTP if the page did not require it.

How best to implement this with Varnish or AWS?