Possible Duplicate:
Tags with usability problems - app.config and web.config

I'm getting a strange bug with one of the synonyms of the tag, .

If you click on it here (or in the list of synonyms) you will go to an invalid webpage.

Is using a tag with a special character like a period allowed?

marked as duplicate by Tim Stone, Won't Mar 1 '12 at 21:44

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • That link doesn't break for me. – Mysticial Mar 1 '12 at 21:03
  • 1
    You have to click on the .java (mind the dot!) link. .java – Nanne Mar 1 '12 at 21:07
  • Oh, ic. It'd be a good idea to redirect those properly. – Mysticial Mar 1 '12 at 21:08
  • Its .brokd.... – amanaP lanaC A nalP A naM A Mar 1 '12 at 21:17
  • @amanaPlanaCAnalPAnaMA ironically that works... – Ben Brocka Mar 1 '12 at 21:24
  • @BenBrocka weird.... I was expecting it not to. – amanaP lanaC A nalP A naM A Mar 1 '12 at 21:27
  • @amanaPlanaCAnalPAnaMA weird indeed... Is there something special with the word java? – fbernardo Mar 1 '12 at 21:28
  • 7
    It seems to happen to any URL ending in .java. For example, this works, but this doesn't, even though the question title is only in the URL for SEO purposes, so it should be ignored in both cases. This makes me suspect it might be the web server treating URLs with a .java extension differently. – hammar Mar 1 '12 at 21:32
  • (^ is status-completed because synonyms were created for the tags, not because IIS was made to behave) – Tim Stone Mar 1 '12 at 21:36
  • 3
    +1 for @hammar. .cs is also broken, as I expected. IIS prevents certain file extensions from being downloaded, .cs (c# file extension) is one of them. So is .config (web.config files). – Won't Mar 1 '12 at 21:38
  • @Won't. That's what I suspected. It also happens to .dll and probably a few more. – hammar Mar 1 '12 at 21:46

90% sure its an IIS thing.

The .NET Framework protects file extensions that should not be directly called by clients by associating them with System.Web.HttpForbiddenHandler in Machine.config. The following file extensions are mapped to System.Web.HttpForbiddenHandler by default: .asax, .ascx, .config, .cs, .csproj, .vb, .vbproj, .webinfo, .asp, .licx, .resx, and .resources [and more not mentioned in this article]


From one of the dupe answers, Phil Haack discusses this in more detail.

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