If you use Sitefinity CMS in continuous integration, testing, or delivery scenarios, you must modify your process. Because of the changes in the bootstrap of a Sitefinity CMS system, you may need to integrate a verification step that checks whether the system is up and running.
The bootstrap process of the system is done asynchronously and the application status page is being displayed while the system is still starting up. This means that page status code that is returned is 200, although Sitefinity CMS is in a process of starting up. This can break your integration tests and deployments, if you rely on successful response as a proof for a running Sitefinity CMS instance.
To ensure that your Sitefinity CMS application is running you should periodically request /appstatus route during application start, while the route is available. This route returns the same status code as the application status page - 200. When this route becomes unavailable - it returns status code 404, it means your application is up and running.
Following are two implementations of this periodical check:
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2021 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity