Forum Discussion
IheartF5_45022
Nacreous
Hi, You can't do exactly what you are asking, however you do have several options;-
- trigger a 'cache invalidation' from the external process that creates new content - this is the most powerful method
- Place low TTL on the cached content
- Use IBR
- Let the application use an IBR-like process by adding a 'cache-buster' query parameter to each request
Are you using a CMS, an off-the-shelf app or a bespoke app?
Do you have a use-case? Otherwise I can give an invalidation trigger example when I wake up (yawn).
AvinashP_138219
Nov 28, 2013Nimbostratus
Hi, thanks for replying on this thread.
I’m working with a Windows engineer (web servers are Windows running IIS) on the first option; using a ‘cache invalidation’ method using the HTTP_LAST_MODIFIED flag in the HTTP header. I’ll also look into the low TTL, thanks for that suggestion.
Could you elaborate some more on IBR and the 'cache-buster' query parameter suggestions ? I haven’t come across those as of yet.
The application running on the web servers is a CMS called Tridion. There’s a piece of software that parses an excel sheet on every request for certain webpages, which generates CPU load on the machines and high response times to the client and presents the parsed output to the client. Caching the parsed output on the LB significantly reduces the CPU load on the boxes.