> But ASP.NET MVC was based on ASP.NET. Which checks for the existence of a file before running any scripts.
This is not correct. When you configure an ISAPI filter in IIS, such as ASP.NET or PHP, you can choose whether or not to verify the presence of files. You can also do this via configuration for .NET HTTP handlers. Parts of ASP.NET itself rely on this feature, such as the trace.axd handler and the web resource handlers.
I don't have the option to verify that you can't create those routes, but if you can't, it's not related to that particular feature.
You can create these routes via ISAPI, but not via ASP.NET (i.e., writing your own .asxd and observe the same borked behavior)--hence why I know the bug's somewhere in ASP.NET proper. You're correct that my post as-written is off, though. I initially thought ASP.NET was hitting files even though I'd told it not to. After more investigation, I think it's blocking those routes as a security feature to protect you in case you at some point turn file routing back on.
Did you check the source? I have never heard of this feature, which certainly doesn't rule it out, but I try to keep abreast of issues like that and haven't heard anything about it.
Comments
> But ASP.NET MVC was based on ASP.NET. Which checks for the existence of a file before running any scripts.
This is not correct. When you configure an ISAPI filter in IIS, such as ASP.NET or PHP, you can choose whether or not to verify the presence of files. You can also do this via configuration for .NET HTTP handlers. Parts of ASP.NET itself rely on this feature, such as the trace.axd handler and the web resource handlers.
I don't have the option to verify that you can't create those routes, but if you can't, it's not related to that particular feature.
You can create these routes via ISAPI, but not via ASP.NET (i.e., writing your own .asxd and observe the same borked behavior)--hence why I know the bug's somewhere in ASP.NET proper. You're correct that my post as-written is off, though. I initially thought ASP.NET was hitting files even though I'd told it not to. After more investigation, I think it's blocking those routes as a security feature to protect you in case you at some point turn file routing back on.
Did you check the source? I have never heard of this feature, which certainly doesn't rule it out, but I try to keep abreast of issues like that and haven't heard anything about it.