Page 1 of 1

Expires On being ignored.

PostPosted: Sun Apr 01, 2012 1:01 pm
by jhb50
It seems that if all items in a web resource specify an expiresOn value that is greater than the console defined expiry period, that the WebResource values are being ignored and the console value used instead.

This makes it impossible to create a groovy that will only refresh at a specific time each day or refresh a month from now which would effectively prevent any automatic refreshes.

Can this be confirmed before I create a ticket?

Re: Expires On being ignored.

PostPosted: Sun Apr 01, 2012 5:54 pm
by zip
Yes, that's correct. The flow is following:

1) check if the feed expired based on the console value
2) if not, check expiresOn for each items, if at least one is expired, expire the whole feed

I'd like to leave it like that to give the user the power to enforce refreshes. As most information is cached anyway it'll not make much difference if the feed itself is refreshed.