{ Community }
  • Academy
  • Docs
  • Developers
  • Resources
    • Community Articles
    • Apigee on GitHub
    • Code Samples
    • Videos & eBooks
    • Accelerator Methodology
  • Support
  • Ask a Question
  • Spaces
    • Product Announcements
    • General
    • Edge/API Management
    • Developer Portal (Drupal-based)
    • Developer Portal (Integrated)
    • API Design
    • APIM on Istio
    • Extensions
    • Business of APIs
    • Academy/Certification
    • Adapter for Envoy
    • Analytics
    • Events
    • Hybrid
    • Integration (AWS, PCF, Etc.)
    • Microgateway
    • Monetization
    • Private Cloud Deployment
    • 日本語コミュニティ
    • Insights
    • IoT Apigee Link
    • BaaS/Usergrid
    • BaaS Transition/Migration
    • Apigee-127
    • New Customers
    • Topics
    • Questions
    • Articles
    • Ideas
    • Leaderboard
    • Badges
  • Log in
  • Sign up

Get answers, ideas, and support from the Apigee Community

  • Home /
  • Edge/API Management /
avatar image
0
Question by Mohammad Ilyas Shah · Apr 13, 2020 at 03:17 PM · 46 Views cachepopulate cache

Deprecated [TimeoutInSec] in expiry settings in Populate Cache policy

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.

Comment
Add comment
10 |5000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by Apigeeks only
  • Viewable by the original poster
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Close

1 Answer

  • Sort: 
avatar image
1
Best Answer

Answer by Dino-at-Google   · Apr 13, 2020 at 10:45 PM

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.

Comment
Add comment Show 4 · Link
10 |5000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by Apigeeks only
  • Viewable by the original poster
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Mohammad Ilyas Shah · Apr 14, 2020 at 04:40 AM 0
Link

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

avatar image Dino-at-Google ♦♦ Mohammad Ilyas Shah   · 5 days ago 0
Link

No, the exact opposite.

avatar image Mohammad Ilyas Shah · Apr 14, 2020 at 05:07 AM 0
Link

<TimeoutInSeconds>259200</TimeoutInSeconds>

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

is this valid?

avatar image Dino-at-Google ♦♦ Mohammad Ilyas Shah   · 5 days ago 0
Link

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

Follow this Question

Answers Answers and Comments

71 People are following this question.

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Related Questions

How are concurrent writes managed using populate cache policy 1 Answer

Store the data into cache and retrive data from cache 3 Answers

Apigee can not retreive data from Cache 1 Answer

Cache transaction details instead of the application session 3 Answers

Javascript JSON object not being cached 1 Answer

  • Products
    • Edge - APIs
    • Insights - Big Data
    • Plans
  • Developers
    • Overview
    • Documentation
  • Resources
    • Overview
    • Blog
    • Apigee Institute
    • Academy
    • Documentation
  • Company
    • Overview
    • Press
    • Customers
    • Partners
    • Team
    • Events
    • Careers
    • Contact Us
  • Support
    • Support Overview
    • Documentation
    • Status
    • Edge Support Portal
    • Privacy Policy
    • Terms & Conditions
© 2021 Apigee Corp. All rights reserved. - Apigee Community Terms of Use - Powered by AnswerHub
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Post an idea
  • Spaces
  • Product Announcements
  • General
  • Edge/API Management
  • Developer Portal (Drupal-based)
  • Developer Portal (Integrated)
  • API Design
  • APIM on Istio
  • Extensions
  • Business of APIs
  • Academy/Certification
  • Adapter for Envoy
  • Analytics
  • Events
  • Hybrid
  • Integration (AWS, PCF, Etc.)
  • Microgateway
  • Monetization
  • Private Cloud Deployment
  • 日本語コミュニティ
  • Insights
  • IoT Apigee Link
  • BaaS/Usergrid
  • BaaS Transition/Migration
  • Apigee-127
  • New Customers
  • Explore
  • Topics
  • Questions
  • Articles
  • Ideas
  • Badges