Bounty Ended with 150 reputation awarded by Ian Robinson
2 Blow out inaccurate statements.
source | link

The 404 is because IISASP.NET is not finding a file called "Blogs". That wildcard mapping kicks in after IIS locates the file in the filesystem. It's just saying that all files should be processed (interpreted) by aspnet_isapi.dll

IIS looks for files first before calling any application frameworks to process the files. By default this is just the standard one-to-one URL-to-filesystem mapping. Once the files is found in the filesystem then it can send the contents of that file to the app framework (in this case ASP.NET).

You will need to put something (a differentcustom routing engine or a URL rewriter) in place that maps URL's to files. Try Helicon's ISAPI Rewrite or Ionic's Isapi Rewrite.

The 404 is because IIS is not finding a file called "Blogs". That wildcard mapping kicks in after IIS locates the file in the filesystem. It's just saying that all files should be processed (interpreted) by aspnet_isapi.dll

IIS looks for files first before calling any application frameworks to process the files. By default this is just the standard one-to-one URL-to-filesystem mapping. Once the files is found in the filesystem then it can send the contents of that file to the app framework (in this case ASP.NET).

You will need to put something (a different routing engine or a URL rewriter) in place that maps URL's to files. Try Helicon's ISAPI Rewrite or Ionic's Isapi Rewrite.

The 404 is because ASP.NET is not finding a file called "Blogs". It's just saying that all files should be processed (interpreted) by aspnet_isapi.dll

You will need to put something (a custom routing engine or a URL rewriter) in place that maps URL's to files. Try Helicon's ISAPI Rewrite or Ionic's Isapi Rewrite.

1
source | link

The 404 is because IIS is not finding a file called "Blogs". That wildcard mapping kicks in after IIS locates the file in the filesystem. It's just saying that all files should be processed (interpreted) by aspnet_isapi.dll

IIS looks for files first before calling any application frameworks to process the files. By default this is just the standard one-to-one URL-to-filesystem mapping. Once the files is found in the filesystem then it can send the contents of that file to the app framework (in this case ASP.NET).

You will need to put something (a different routing engine or a URL rewriter) in place that maps URL's to files. Try Helicon's ISAPI Rewrite or Ionic's Isapi Rewrite.