Microsoft has deprecated wfastcgi so it shouldn't be used any more.
If people start cleanly with HttpPlatformHandler, the experience should be smooth,
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<handlers>
<add name="httpPlatformHandler" path="*" verb="*" modules="httpPlatformHandler" resourceType="Unspecified" requireAccess="Script" />
</handlers>
<httpPlatform stdoutLogEnabled="true" stdoutLogFile=".\python.log" startupTimeLimit="20" processPath="C:\Users\<user name>\AppData\Local\Programs\Python\Python310\python.exe" arguments=".\mysite\manage.py runserver %HTTP_PLATFORM_PORT%">
</httpPlatform>
</system.webServer>
</configuration>
Python/Django still takes care of everything including static files, and IIS/HttpPlatformHandler just passes requests on.
More details can be found from my blog post.
Microsoft has deprecated
wfastcgiso it shouldn't be used any more.If people start cleanly with HttpPlatformHandler, the experience should be smooth,
Python/Django still takes care of everything including static files, and IIS/HttpPlatformHandler just passes requests on.
More details can be found from my blog post.