Skip to content

Commit b95ea6e

Browse files
authored
Merge pull request #67392 from cephalin/issue#14667
#14667
2 parents a4b3275 + b737681 commit b95ea6e

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/app-service/deploy-staging-slots.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,9 @@ When using [Auto-Swap](#Auto-Swap), some apps may require custom warm-up actions
201201
</applicationInitialization>
202202
</system.webServer>
203203

204-
You can also customize the warm-up behavior with one or more of the following [app settings](https://github.com/MicrosoftDocs/azure-docs-pr/pull/web-sites-configure.md):
204+
For more information on customizing the `applicationInitialization` element, see [Most common deployment slot swap failures and how to fix them](https://ruslany.net/2017/11/most-common-deployment-slot-swap-failures-and-how-to-fix-them/).
205+
206+
You can also customize the warm-up behavior with one or more of the following [app settings](web-sites-configure.md):
205207

206208
- `WEBSITE_SWAP_WARMUP_PING_PATH`: The path to ping to warmup your site. Add this app setting by specifying a custom path that begins with a slash as the value. For example, `/statuscheck`. The default value is `/`.
207209
- `WEBSITE_SWAP_WARMUP_PING_STATUSES`: Valid HTTP response codes for the warm-up operation. Add this app setting with a comma-separated list of HTTP codes. For example: `200,202` . If the returned status code is not in the list, the warmup and swap operations are stopped. By default, all response codes are valid.

0 commit comments

Comments
 (0)