varnish as general purpose web cache

[Guillaume Quintard]

Are we talking about HTTP or HTTPS here?

In the first case, you can use dynamic backends to point at arbitrary hosts.

HTTPS is doable but it's going to be another can of worms because varnish
basically need to be a man-in-the-middle and you'll need special
certificates on all the clients.

On Sun, Nov 3, 2019, 09:18 Sven Oehme <oehmes at gmail.com> wrote:

> i can't create a cache as the content is non predictable and comes
> from various sources. i also can't change the tool thats accessing the
> files unfortunate. as i said, a very special case :-)
> the only way i see i can solve this is simply cache all accessed data
> via http, lets see if squid can do it.
>
> sven
>
> On Sun, Nov 3, 2019 at 10:12 AM Rainer Duffner <rainer at ultra-secure.de>
> wrote:
> >
> >
> >
> > Am 03.11.2019 um 18:10 schrieb Sven Oehme <oehmes at gmail.com>:
> >
> > my case is very special. all the nodes download several GB size files
> > and they are all static, think more about a CDN case. i will take a
> > look at squid.
> >
> >
> >
> > Then create a local cache and point the nodes there?
> >
> > Varnish exists because Squid has a number of fundamental problems.
> > Those problems didn’t go away in the last two decades ;-)
> >
> >
> >
> >
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20191103/0651a209/attachment.html>