You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked how EpiServer (DXC) handles site warmup and according to documentation they use IIS built in tool of applicationInitialization. This assumes that there's a list of urls in the web.config to be visited before site is considered to be ready.
What DXC is doing is that they try to build such list by visiting root page and trying to find (and visit) all relative links which obviously might not be enough. So solution seems to be building such list manually, per project, and putting it into web.config (web config transformation to be specific).
So, my undestanding is that any attempt of doing it from code (this nuget) is meaningless as any code which we will prepare will be run after page is initialized so also after applicationInitialization tool is run.
Ideally this tool should warmup (by visiting?) each PageType defined in EpiServer.
The text was updated successfully, but these errors were encountered: