Content-Range header problem

[Nathan Kinkade]

On Wed, Sep 16, 2009 at 1:41 PM, Kristian Lyngstol
<kristian at redpill-linpro.com> wrote:
> On Wed, Sep 16, 2009 at 01:36:00PM -0400, Nathan Kinkade wrote:
>> Thanks.  The resolution is simple, but I just wanted to be sure.
>
> Always nice to verify :)
>
> By the way, I just read the labs.cc.o post [1] from when you started using
> Varnish and I'm curious as to how you're doing now with regards to these
> issues?
>
> [1] http://labs.creativecommons.org/2008/04/03/varnish-cache-at-cc/

I haven't actually checked the issue with 600M+ files.  It's not often
that we're hosting anything that big.  In any case, since that time
there have been no complaints or problem related to any large file.
Anyway, I suppose it's better to explicitly pipe directly to Apache
any requests for ISO CD images. :-)

Bazaar.  It happens that we don't do anything with Bazaar really.  It
was a coincidence that at the time I was writing a plugin for Planet
Venus (feed aggregator) and those devs use Bazaar so I had been trying
to make my patches available to them.  That issue just sort of went
away and we haven't had any reason to use Bazaar since, though we have
used git and subversion quite a lot through Varnish without any issue.

The bbPress issue seems to have gone away as well.

The Apache KeepAlive issue was fixed at some point and I turned it
back on a long time ago.

The log file size issue was resolved by simply upgrading all the
machines to amd64 distribution of Debian.  Doing that remotely and
in-place was outlined here:

http://labs.creativecommons.org/2008/07/15/32-to-64bit-remotely/

We love Varnish at CC.

Thanks!

Nathan