London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
Caching not working in Azure
According to Quan's post from August 2017 there is a bug in .NET 4.7: https://vimvq1987.com/episerver-caching-issue-net-4-7/
We are running Episerver.Find version 12.5.3. The Azure env. is running .NET 4.7.1, where this .NET bug is fixed.
Edited,
Mar 20, 2018 15:30
There are 2 related bugs being worked on:
Edited,
Mar 21, 2018 7:46
Thanks for the update, Jonas. Yes, we confirmed yesterday that the issue disappeared when scaling down to 1 instance.
Mar 21, 2018 8:25
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
We are using Find heavily on our site, and have added caching using
or
I have added proxy settings to web.config and verified that caching is working locally (query is exceuted once).
But on Azure we get a lot of errors indicating that the results are not cached (EPiServer.Find.ServiceException: The remote server returned an error: (429) Too Many Requests.)
Anyone seen similar behavior? Or know what to look for?