Support for If-None-Match header.

[Guillaume Quintard]

*set up, sorry, fat fingers. I haven't studied the question in depth, but
i'm pretty sure you can bend varnish's arm and do what you ask, but that's
complicated.

Regarding your second question, Varnish doesn't need to check the origin if
the origin pushes the bans directly.

-- 
Guillaume Quintard

On Mon, Jan 23, 2017 at 3:05 PM, Jan Hugo Prins | BetterBe <
jprins at betterbe.com> wrote:

> What do you mean by "unless you want some very involved set"?
> And sure, Varnish can ban objects when they become invalid, but then it
> still needs to check the origin to see if the object is still valid.
>
> Jan Hugo
>
>
>
> On 01/23/2017 02:47 PM, Guillaume Quintard wrote:
>
> Hi,
>
> Short answer is : no, unless you want some very involved set.
>
> BUT, what you can do is: let varnish work its magic, and just ban objects
> based on ETAG when they become invalid.
>
> --
> Guillaume Quintard
>
> On Mon, Jan 23, 2017 at 1:56 PM, Jan Hugo Prins | BetterBe <
> jprins at betterbe.com> wrote:
>
>> Hello,
>>
>> We are currently investigating the use of Varnish for our infrastructure.
>> In the software we build, we depend on the If-None-Match header and the use
>> of ETAG's.
>> The API we have created creates mainly JSON objects, and they differ in
>> size from a few hundreds of bytes to several megabytes. A lot of these JSON
>> objects are perfectly suited for caching, until someone changes a parameter
>> and this can happen at any moment. That is also why we keep a record of all
>> ETAG's and we invalidate them when needed.
>>
>> What we would like to do is cache created JSON object in front of our
>> production environment and when someone requests the same calculation that
>> someone else has requested before and the ETAG is still valid, send out the
>> cached object. But this basicly implies the following workflow:
>>
>>
>>
>> Somewhere I found an old Trac Wiki document that describes something like
>> this, but I can't figure out if this has been implemented or not.
>> https://www.varnish-cache.org/trac/wiki/BackendConditionalRe
>> quests?version=8
>>
>> Could someone tell me if the workflow I describe is possible? My first
>> tests tell me that in the default setup it isn't working like this.
>>
>> Best regards,
>> Jan Hugo Prins
>>
>>
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
> --
>
> Met vriendelijke groet / Best regards,
>
> Jan Hugo Prins
> *Infra and Storage consultant*
> [image: BetterBe - Transforming automotive leasing worldwide]
> <https://www.betterbe.com>
> Auke Vleerstraat 140 E *T* +31 (0) 53 48 00 694
> <+31%20%280%29%2053%2048%2000%20694>
> 7547 AN Enschede *E* jprins at betterbe.com
> CC no. 08097527
> <https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=080975270000>
> *M* +31 (0)6 26 358 951 <+31%20%280%296%2026%20358%20951> www.betterbe.com
> BetterBe accepts no liability for the content of this email, or for the
> consequences of any actions taken on the basis of the information provided,
> unless that information is subsequently confirmed in writing. If you are
> not the intended recipient you are notified that disclosing, copying,
> distributing or taking any action in reliance on the contents of this
> information is strictly prohibited.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170123/4ce60032/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: betterbe_handtekening_v1_logo.png
Type: image/png
Size: 10832 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170123/4ce60032/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 112886 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170123/4ce60032/attachment-0003.png>