46

Someone created the other day. Being a dutiful member of the New Tag Deletionist Cabal, I dove in to try and see if there could be a better, existing tag for the question, only to be greeted with nothing. The server returned 404, a Date header, and a content length of zero.

This is a known behavior with IIS that has bit SO before.

Given that this is known IIS behavior, the tagging system should make an effort to block users from creating new tags that will result in the site breaking.

(As for , I was able to find the question and replace the tag with )

Improve this question
5
  • 7
    Isn't the real solution to not have them trigger the filter to begin with? Not sure what kind of problems are involved with that, but it makes sense to me.
    – user159834
    Apr 11, 2012 at 17:41
  • 6
    Since this can be fixed (supposedly) when we move to MVC v4, it seems like this would be for a short-term benefit. I think it's better to wait and see if we can take care of all these extensions and use those valid tag names.
    – Nick Craver
    Apr 11, 2012 at 18:00
  • Interesting. When will you know whether or not it can be fixed with the move to MVC 4? Rather, will you be playing with the beta, or is this something that would be looked into only after it's out of beta?
    – Charles
    Apr 11, 2012 at 19:54
  • @Charles - Let me say this: "maybe". Stack Overflow itself was created with the first beta of ASP.Net MVC...so who knows. It's not a top priority at the moment, we have other major things behind the scenes that are first up.
    – Nick Craver
    Apr 11, 2012 at 23:08
  • Related: meta.stackexchange.com/questions/136767/…
    – Abe Karplus
    Jul 27, 2012 at 4:38

1 Answer 1

Reset to default
7

After the next build we will allow extensions that were previously restricted. We have updated to ASP.NET MVC4 and it appears to handle them correctly.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .