-
Notifications
You must be signed in to change notification settings - Fork 59
Support app_offline.htm #81
Comments
Hosting already supports Ctl+C and Ctl+Break. |
Cool, thanks for checking! |
Note for HPH side: CreateProcess will need to be called the right way with the flag |
HPH will be checking periodically for the presence of this file? I wish checking for the file file could be disabled in options for |
@guardrex - why? |
Perf concern ... How often does HPH have to check for the file? Is it inconsequential (i.e., milliseconds spent every several seconds ... i.e., that's no "concern" to be concerned about)? |
edit: @guardrex beat me by about 20 secs. ha doh. |
@guardrex - Perf concern - I would assume that platform handler will not poll but be notified about changes. Not sure how much overhead it would add but IIS already monitors changes to the web.config file and I don't think this is causing perf issues.
I guess this is always true - overwriting the .exe containing the app will have the same effect and you can take the site down just by overriding the web.config file. |
Perfect! ...... concern withdrawn. |
@guardrex On a related note, HPH is configured exclusively via the web.config. There's nothing you/we can do once the app has launched. UseIISPlatformHandler and similar just consume things provided by HPH. |
@Tratcher I see. Just asking. I'm good. |
When VS is used we will pass the |
👍 |
This as been fixed in AspNetCoreModule v0.8: #105. |
For anyone who happens upon this thread in the future, it should be noted that there are versions of the .Net Core Module that only respect all lower case "app_offline.htm". (see comments here: https://docs.microsoft.com/en-us/aspnet/core/hosting/aspnet-core-module). There is mention of this being fixed in the latest version, but it isn't clear which version. |
It was fixed in Version 1.0.1971. |
Initial HPH work completed by end of Feb.
Deployer developed in parallel
Update publish-iis to add signalShutdown to the web.config
RE: aspnet/Hosting#141
@sayedihashimi
The text was updated successfully, but these errors were encountered: