Skip to content

Commit 229e302

Browse files
authored
Update FAQ formatting and wording for clarity
Edit review per CI 5433
1 parent 2a065a8 commit 229e302

1 file changed

Lines changed: 7 additions & 5 deletions

File tree

support/azure/app-service/faqs-app-service-linux.yml

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -250,17 +250,19 @@ sections:
250250
- question: |
251251
How does the container warmup request work?
252252
answer: |
253-
When Azure App Services starts your container, the warmup request sends an HTTP request to the [/robots933456.txt](/azure/app-service/configure-custom-container?pivots=container-linux#robots933456-in-logs) endpoint of your application. This is simply a dummy endpoint, but your application needs to reply with any status code (including 5xx). If your application logic doesn't reply with any HTTP status code to nonexistent endpoints, the warmup request can't receive a response and it perpetually restarts your container.
254-
The warmup endpoint path and the status codes that consider the site warmed-up can be customized from the default behavior by setting the [WEBSITE_WARMUP_PATH](/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#app-environment) and [WEBSITE_WARMUP_STATUSES](/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#app-environment) application settings.
255-
The warmup request also might fail due to port misconfiguration.
253+
When Azure App Services starts your container, the warmup request sends an HTTP request to the [/robots933456.txt](/azure/app-service/configure-custom-container?pivots=container-linux#robots933456-in-logs) endpoint of your application. This is simply a dummy endpoint, but your application must reply by returning any status code (including 5*xx*). If your application logic doesn't reply by sending an HTTP status code to nonexistent endpoints, the warmup request can't receive a response. Therefore, it perpetually restarts your container.
256254
257-
To ensure that the port is correctly configured on Azure App Services, see the question *How do I specify port in my Linux container?*
255+
To change from the default behavior, you can customize the warmup endpoint path and status codes that consider the site to be warmed up. To do this, set the [WEBSITE_WARMUP_PATH](/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#app-environment) and [WEBSITE_WARMUP_STATUSES](/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#app-environment) application settings.
256+
257+
The warmup request also might fail because of port misconfiguration.
258+
259+
To make sure that the port is correctly configured on Azure App Services, see the question, *How do I specify the port in my Linux container?*
258260
- question: |
259261
Is it possible to increase the container warmup request timeout?
260262
answer:
261263
The warmup request by default fails after waiting 240 seconds for a reply from the container. You may increase the container warmup request timeout by adding the application setting `WEBSITES_CONTAINER_START_TIME_LIMIT` with a value between 240 and 1800 seconds.
262264
- question: |
263-
How do I specify port in my Linux container?
265+
How do I specify the port in my Linux container?
264266
answer: |
265267
| Container type | Description | How to set/use port |
266268
|----------------|-------------|---------------------|

0 commit comments

Comments
 (0)