Deprecated [TimeoutInSec] in expiry settings in Populate Cache policy

mohdilyas
Participant IV

I just found out from the docs that the TimeOutInSec setting in the populate cache policy is deprecated now and should be replaced with TimeOutInSeconds.

I have some API proxies in production which are using the PC policy with [TimeOutInSec] and I want to know if this change is going to affect them?

Thanks

FYI: I tried to upload an image here but there seems some issue with the upload feature.

Solved Solved
0 5 179
1 ACCEPTED SOLUTION

No, the old property will still work, just as it always has worked.

The old property (TimeOutInSec) does not de-reference the ref= attribute. The new property (TimeOutInSeconds) does de-reference the ref= attribute if one exists.

If you don't have a ref= attribute, then they are equivalent.

Your existing policies will continue to work unchanged.

View solution in original post

5 REPLIES 5

No, the old property will still work, just as it always has worked.

The old property (TimeOutInSec) does not de-reference the ref= attribute. The new property (TimeOutInSeconds) does de-reference the ref= attribute if one exists.

If you don't have a ref= attribute, then they are equivalent.

Your existing policies will continue to work unchanged.

So what I understood is: We cannot use ref attribute with the new property but can be used with old one. Correct?

No, the exact opposite.

<TimeoutInSeconds>259200</TimeoutInSeconds>

<TimeoutInSec ref="resetPasswordLinkExpiryTimeInSeconds">259200</TimeoutInSec>

is this valid?

ref= is accepted with either. It is non-functional with the original TimeOutInSec.