Skip to content

Corrected warmup path status code info and added references for customizing warmup path #1858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Corrected warmup path status code info and added references for customizing warmup path #1858

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
da6836b
Corrected website warmup information and added refs to settings
adamkimsft Apr 14, 2025
2a065a8
Corrected links to use bookmarks
adamkimsft Apr 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion support/azure/app-service/faqs-app-service-linux.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,7 +250,8 @@ sections:
- question: |
How does the container warmup request work?
answer: |
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 non-5XX status code. 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.
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.
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.
The warmup request also might fail due to port misconfiguration.

To ensure that the port is correctly configured on Azure App Services, see the question *How do I specify port in my Linux container?*
Expand Down