Best practice for caching scenario with different backend servers but same content

[Geoff Simmons]

On 8/9/21 14:49, Geoff Simmons wrote:
> 
> A hash algorithm computes a number h(b) for a backend b, ...

Sorry, this should have been more like h(bereq), meaning that the number
is computed from features of the request. From that you get to the
choice of a backend.

The Varnish hash director uses the same hash value that was computed for
caching.

The shard director also does that by default, but some other choices can
be set with the parameter by in shard.backend(): by=HASH (default),
by=URL, by=KEY, by=BLOB


Geoff
-- 
** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20210809/28a84255/attachment.bin>