Closed ala53 closed 8 years ago
Check your web.config and see if forwardWindowsAuthToken=false is set, if it is, remove it and try deploying again.
It is not. The contents of web.config are:
<configuration>
<system.webServer>
<handlers>
<add name="httpplatformhandler" path="*" verb="*" modules="httpPlatformHandler" resourceType="Unspecified" />
</handlers>
<httpPlatform processPath="%home%\site\approot\web.cmd" arguments="" stdoutLogEnabled="false" stdoutLogFile="\\?\%home%\LogFiles\stdout.log" startupTimeLimit="3600"></httpPlatform>
</system.webServer>
</configuration>
set stdoutLogEnabled=true and take a look at the logs. Also take a look at the event log.xml and see if there's anything interesting in there.
@ala53 Could you provide us a simplified repro code?
Hello As requested: https://github.com/ala53/iis-error-sample It is hosted here: http://zsb-test-123.azurewebsites.net/
Unfortunately, the initial post is wrong. It isn't a problem with IIS on all systems. It only occurs when using the Visual Studio auto deploy to azure.
See here: http://zsb-test-123.azurewebsites.net/this-will-work-fine.com and http://zsb-test-123.azurewebsites.net/http://this-will-crash-the-server.com When hosted locally, it works fine.
@Tratcher
The entire issue can be reproduced via this:
[HttpGet, Route("/{*routeData}")]
public string HttpGetRoutedData(string routeData)
{
return "Your route data was: " + routeData;
}
@BrennanConroy Can you investigate?
This is an Antares issue, I have contacted them to see if they can resolve it.
Note this also repros with Asp.Net 4 on azure web sites.
I'm also getting issue. The character causing the problem appears to be the colon.
If that route is called with
/Important/http://github.com
, it works on Kestrel but errors on IIS (at least through auto-deploy azure). The error is: Config Error: Cannot read configuration file Config File: \?\D:\home\site\wwwroot\Important\http:\web.config ...claiming the physical path is Physical Path: D:\home\site\wwwroot\Login\http:\github.comIn short form, ASP.net doesn't hook the URL...and IIS can't find any to match.