Re: running varnish-2.0.2 on Sun

2009-02-13 Thread Armando Singer
>> | Does anyone have an idea what has caused this? >> >> Not really, no. I'm going to get a buildbot slave going on Solaris so >> we'll hopefully be able to avoid such bugs in the future. If you have >> found a solution, patches are more than welcome. >> > We set VCC_CC in config.h to be gcc rat

Re: Configuration question about a domain list for a http.req.host comparaison

2009-02-13 Thread Damien Desmarets
Tollef Fog Heen a écrit : > ]] Damien Desmarets > > | I have 1 question for you. I haven't found the response in the > | documentation/wiki. I think you have a big job to wrtie a good > | documentation ... the current is really poor ! > > If you want to help out with writing docs or suggest weak p

Re: Varnish and virtual hosting

2009-02-13 Thread Kitai
> >> 3. There doesn't seem to be a way to process live varnishncsa data >> via a pipe. If this were possible, then I think I would find this whole >> process a lot easier. Instead, it seems there are two options: to >> historically dump log data via an option, or run as a daemon and send >> out

AW: Varnish and mp3 streaming on demand

2009-02-13 Thread Andreas Fassl (proGIS)
If I use varnish as cache between mp3 repository and lighttpd, lighttpd will stream the cached contents, that is sufficient for us. If varnish could stream, that would be fine, but I don't think that it is part of the original concept, or? - Originalnachricht - Von: Dag-Erling Smørgr

Re: [varnish] Re: Default behaviour with regards to Cache-Control

2009-02-13 Thread Ricardo Newbery
On Feb 13, 2009, at 4:54 AM, Dag-Erling Smørgrav wrote: > Ole Laursen writes: >> I looked up private here >> >> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html >> >> and it says >> >>Indicates that all or part of the response message is intended >>for a single user and MUST NOT b

Re: Default behaviour with regards to Cache-Control

2009-02-13 Thread Ole Laursen
Dag-Erling Smørgrav writes: > Varnish is not a shared cache, it's a surrogate (not covered by RFC2616) The only reason I quoted the RFC was to explain why I was surprised that my web app broke: Cache-Control: private is a strong hint that the object cannot be shared between users. Ole __

Re: Varnish and virtual hosting

2009-02-13 Thread Dag-Erling Smørgrav
Justin Finkelstein writes: > 1. There didn't seem to be a way to seperate out log data for each > virtual host using varnishncsa. Correct. This has been discussed in the past, search the list archives. > 2. There doesn't seem to be a way to get log data out of varnish in > a 'live' fash

Re: Varnish and mp3 streaming on demand

2009-02-13 Thread Dag-Erling Smørgrav
"Poul-Henning Kamp" writes: > No, we never stream pass, the current design is aimed at freeing > up the backend as fast as possible, and we only start to transmit > the object to the client once we have all of it. Perhaps it is time to consider adding a third option: "stream", which streams the c

Re: Default behaviour with regards to Cache-Control

2009-02-13 Thread Dag-Erling Smørgrav
Ole Laursen writes: > I looked up private here > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html > > and it says > > Indicates that all or part of the response message is intended > for a single user and MUST NOT be cached by a shared cache. This > allows an origin server to

Re: Varnish and mp3 streaming on demand

2009-02-13 Thread Ole Laursen
Poul-Henning Kamp writes: > >Right now pass in vcl_recv is streaming, right? > >You're only talking about if the > >object is entered into the cache? Or both cases? > > No, we never stream pass, the current design is aimed at freeing > up the backend as fast as possible, and we only start to tra

Re: Varnish and mp3 streaming on demand

2009-02-13 Thread Poul-Henning Kamp
In message , Ole Laursen writes: >Poul-Henning Kamp writes: > >> This is necessary to be able to decide, per object, if it should be >> stored in temporary (malloc) or persistent (disk) storage. >> >> With some extra work, this will allow pass to become streaming. > >Right now pass in vcl_recv is

Re: Varnish and mp3 streaming on demand

2009-02-13 Thread Ole Laursen
Poul-Henning Kamp writes: > This is necessary to be able to decide, per object, if it should be > stored in temporary (malloc) or persistent (disk) storage. > > With some extra work, this will allow pass to become streaming. Right now pass in vcl_recv is streaming, right? You're only talking ab

Re: running varnish-2.0.2 on Sun

2009-02-13 Thread Rob Ayres
2009/2/12 Tollef Fog Heen > ]] Rob Ayres > > | Does anyone have an idea what has caused this? > > Not really, no. I'm going to get a buildbot slave going on Solaris so > we'll hopefully be able to avoid such bugs in the future. If you have > found a solution, patches are more than welcome. > >

Re: Varnish and mp3 streaming on demand

2009-02-13 Thread Ole Laursen
Andreas Fassl writes: > Hi, especially the caching is very important for us, because we want to > keep traffic away from the mp3 repository server. > So you recommend: > Client requests streaming on demand mp3 > - lighthttpd does streaming and requests from > - varnish as reverse proxy/cache from

Varnish and virtual hosting

2009-02-13 Thread Justin Finkelstein
Hi guys I'm fairly new to Varnish and it's goodness and not that brilliant a sysadmin (I'm a developer, really) and I have some questions about how to go about setting up Varnish in a virtual hosting environment. I've had a lot of trouble combining the technologies I use for non-proxied hosting

Re: ESI include: src, alt, onerror weirdness

2009-02-13 Thread Per Andreas Buer
- "Florian Gilcher" wrote: > Skade Added to the "wiki" group. -- Redpill Linpro - Changing the Game ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: ESI include: src, alt, onerror weirdness

2009-02-13 Thread Florian Gilcher
On Feb 13, 2009, at 9:27 AM, Tollef Fog Heen wrote: > ]] Florian Gilcher > > | > | How about the unexpected break when retrieving an empty document? > > That's weird. Can you try again using 2.0.3? Same issue. I'll report it. > | [1]: And undocumented. The documentation sadly leads to believe