Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture.
minor feature: Fail VCL loading if VMOD objects are left uninitialized.. Report the VCL name of the uninitialized object.. vmodtool generated RST headers.. test that structural tags are included in a (-w)ritten log.. Test that director with sick backends only is shown as sick.. doc tlc.. Properly prethe arg structures.. Flexelinting.. Park in a XXX comment, pending API renovation.. Test that NULL-object handling also copes with 2297.. Kill redundant redundant null checks.. Reduce -margin over highest known filedescriptor.. Null check.. Null check.. Null check, hat trick.. Null check.. Report what we did get, if we EOF while receiving header.. Make this test more resistant to machine overload.. Allow non-fatal (usually server) rxhdrs to fail silently.. Stabilize this test under heavy system loads.. Show VDPs if present during a panic.. Guard all the VDP_Push calls.. Consume less random bits, and don't pace after ramp-up.. Optimize varnishtests central scheduler.. Implement an optional high performance "cleaner".. The GCC people are getting ridiculous.. add debit to count contended locks.. oversight from previous commit.. Don't increment the contested counter until we have the lock.. Typo.. Typo in my typo. Improse FetchError on first byte timeout.. Insist that VCL_RET_FAIL goes through VRT_fail() and not VRT_handling().. Refactor our "call into VCL" code a little.. stop using "purge" in the context of bans.. Don't panic if you try to relabel a VCL with the same label.. improve beresp.filters doc.. I forgot the simplest of them all.. VDP_Push itself is not fail-safe.. retire undocumented backend.list -v option.. b00016.vtc.. Add bans on obj.ttl, obj.age, obj.grace and obj.keep.. changelog..