![]() WEBSITE_WARMUP_PATH: A relative path on the site that should be pinged whenever the site restarts (not only during slot swaps). By default, all response codes are valid. If the returned status code isn't in the list, the warmup and swap operations are stopped. Add this app setting with a comma-separated list of HTTP codes. WEBSITE_SWAP_WARMUP_PING_STATUSES: Valid HTTP response codes for the warm-up operation. Add this app setting by specifying a custom path that begins with a slash as the value. WEBSITE_SWAP_WARMUP_PING_PATH: The path to ping over HTTP to warm up your site. You can also customize the warm-up behavior with one or both of the following app settings: Here's a sample web.config fragment from the azure doc: The swap operation waits for this custom warm-up to finish before swapping with the target slot. ![]() The applicationInitialization configuration element in web.config lets you specify custom initialization actions. ![]() If I understand correctly, you want to know what needs to happen for the slot to be "warm" completely?Īdding to AndriyBilous response and the thread he referenced- to ensure the slot is warmed up completely use the Application Initialization Module to warm up the slot prior to swapping it into production. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |