that work or am I missing some pieces that would screw up
the plan?
Thanks,
--DHF
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
andan andan wrote:
> We have a security doubt: Should we install Varnish inside or outside
> firewall?
I run varnish on a many linux boxes with Netfilter default log and drop
rules and have not seen a performance problem.
> For better performance, we consider that the best choice is outside,
> bu
Jon Drukman wrote:
> i'm trying to rewrite all incoming URLs to include the http host header
> as part of the destination url. example:
>
> incoming: http://site1.com/someurl
> rewritten: http://originserver.com/site/site1.com/someurl
>
> incoming: http://site2.com/otherurl
> rewritten: http://or
Calle Korjus wrote:
> This is our startup command:
>
> /opt/varnish/sbin/varnishd -a :80 -p lru_interval 3600 -f
> /opt/varnish/conf/default.vcl -T 127.0.0.1:6082 -t 3600 -w 128,1000,60 -u
> varnish -g varnish -s file,/srv/varnish/varnish_storage.bin,30G -P
> /var/run/varnish.pid
>
> Varnish loo
Ricardo Newbery wrote:
>
> On Apr 7, 2008, at 10:30 PM, DHF wrote:
>
>> Ricardo Newbery wrote:
>>> On Apr 7, 2008, at 5:22 PM, Michael S. Fischer wrote:
>>>
>>>
>>>> Sure, but this is also the sort of content that can be cached back
>>
Ricardo Newbery wrote:
> On Apr 7, 2008, at 5:22 PM, Michael S. Fischer wrote:
>
>
>> Sure, but this is also the sort of content that can be cached back
>> upstream using ordinary HTTP headers.
>>
>
>
> No, it cannot. Again, the use case is dynamically-generated content
> that is subject
Sascha Ottolski wrote:
> Am Freitag 04 April 2008 18:11:23 schrieb Michael S. Fischer:
>
>> Ah, I see.
>>
>> The problem is that you're basically trying to compensate for a
>> congenital defect in your design: the network storage (I assume NFS)
>> backend. NFS read requests are not cacheable by
Sascha Ottolski wrote:
> however, my main problem is currently that the varnish childs keep
> restarting, and that this empties the cache, which effectively renders
> the whole setup useless for me :-( if the cache has filled up, it works
> great, if it restarts empty, obviously it doesn't.
>
>
Michael S. Fischer wrote:
> On Thu, Apr 3, 2008 at 10:26 AM, Sascha Ottolski <[EMAIL PROTECTED]> wrote:
>
>> All this with 1.1.2. It's vital to my setup to cache as many objects as
>> possible, for a long time, and that they really stay in the cache. Is
>> there anything I could do to prevent
Sascha Ottolski wrote:
> how can this be? My varnish runs for about 36 hours now. yesterday
> evening, the resident memory size was like 10 GB, which is still way
> below the available 32. later that evening, I stopped letting request
> to the proxy over night. now I came back, let the request b
Sascha Ottolski wrote:
> now, could someone help me interpreting the hitrate ratio and avg?
>
> Hitrate ratio: 10 100 360
> Hitrate avg: 0.3366 0.3837 0.4636
>
Hit rate is the number of hits/number of requests. Hits are requests
for objects that are in the cache, Misses
Sascha Ottolski wrote:
> Hi,
>
> I'm a bit puzzled by the examples and the explanation of the "default"
> vcl config presented in the man page. Now I'm wondering, if I want to
> make my first steps for creating a reverse proxy for static images
> only, that basically should cache everything inde
hot objects without having to use some front end load balancer like
perlbal, big ip or whatever to direct the individual clients to specific
frontlines to accomplish the same thing ( though you usually still have
a load balancer for fault tolerance ). Though in squid there are some
bugs with their imp
13 matches
Mail list logo
