<strike>IIS</strike> ASP.net, by default, prohibits service of many file extensions, `.cs` is one.

So the request is being killed by <strike>IIS</strike> ASP.net before it hits the REST handlers.

This can be fixed fairly easily by striking the following entry, if so desired...

%SYSTEM%\Microsoft.NET\Framework\v2.0.50727\CONFIG\Web.Config

    ....
    <httpHandlers>
       <add path="*.cs" verb="*" type="System.Web.HttpForbiddenHandler" validate="True"/>
    ....

But subverting ASP doesn't seem to be a solution to me. 

Perhaps naked links like that can be rendered with a filter that contains the forbidden extensions and just munge them a bit as systempuntoout has demonstrated.

Or perhaps add a filter to tag creation to prevent such tags from being created. But I think i like the munge better.

But the bottom line is that *something* should be done, otherwise arbitrary numbers of tag links are just going to be bad. It is not so apparent here, but on SO... 


hey, i wonder...

Sure enough   https://stackoverflow.com/questions/tagged/.cs

Nice catch Steffen.


---

And of course this is just my supposition. I am not privy to the inner workings of the SO servers.

But I do have a bit of experience with how an [HttpWorkerRequest][1] behaves.

If anyone needs a better dev server than the one that comes with VS08 or VS10 you can get one [here][2]


  [1]: http://msdn.microsoft.com/en-us/library/system.web.httpworkerrequest.aspx
  [2]: http://cassinidev.codeplex.com/