vcl_purge

[Per Buer]

On Fri, Mar 27, 2015 at 3:27 PM, Jennings III, Raymond <
raymond.jennings at nytimes.com> wrote:

> When things get purged vcl_miss and vcl_hit were handling it just fine for
> me.  I really don't care about the Vary issue.  I just wanted to know if
> the hash on the uri for a purge - was their a match or not.
>

Well. Knowing if there is a hash match rather than knowing if the object
was purge doesn't sound very useful IMO.

"Nobody" - seems odd - I use it extensively.
>

True. I've never heard anyone ask about this. Since Varnish is a cache
people don't usually care about what potentially was there before a PURGE
call. The only thing they care about is whether the purge succeeded or not.

What do you use it for? Why do you care if the purge call purged something?


> On Fri, Mar 27, 2015 at 10:18 AM, Per Buer <perbu at varnish-software.com>
> wrote:
>
>> Hi Raymond.
>>
>> On Fri, Mar 27, 2015 at 3:02 PM, Jennings III, Raymond <
>> raymond.jennings at nytimes.com> wrote:
>>
>>> Can I get access to anything - that is being purged, the obj, if the
>>> purge was successful, anything at all?
>>>
>>> It sucks that vcl_miss and vcl_hit are off the request path (in the vcl
>>> anyway.)
>>>
>>
>> Nobody has ever expressed interest in this before. And Varnish 3 really
>> didn't support it properly (due to Vary:-handling) so it isn't something
>> we've ever supported properly.
>>
>> What is the use case?
>>
>> --
>> *Per Buer*
>> CTO | Varnish Software AS
>> Cell: +47 95839117
>> We Make Websites Fly!
>> www.varnish-software.com
>> [image: Register now]
>> <http://info.varnish-software.com/varnish-summits-autumn-2014-registration>
>>
>
>


-- 
*Per Buer*
CTO | Varnish Software AS
Cell: +47 95839117
We Make Websites Fly!
www.varnish-software.com
[image: Register now]
<http://info.varnish-software.com/varnish-summits-autumn-2014-registration>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20150327/c54c39ab/attachment.html>