5

When clicking on a question tagged , the site produces a 'Page Not Found' error.

3

Pretty sure this isn't a browswer issue. Looks like the tag (and probably some other special cases) may have to be encoded differently to keep ASP.NET from freaking out.

  • I agree. Just being complete in specifying the browser. I suspect that somewhere, the .aspx is causing an incorrect redirection to a non-existant page. – Jeff Yates Aug 4 '09 at 14:07
  • Agreed, likely a bug than a browser issue – Aaron Aug 4 '09 at 14:22
  • 1
    This also happens with ".config" – Brad Gilbert Aug 4 '09 at 14:41
  • 1
    It is likely to occur for a variety of different asp.net extensions – TheTXI Aug 4 '09 at 14:47
2

Also note this only happens with ASP.NET related-extensions (e.g. .aspx and .config). As in, the .net tag and nonexistent .foo tag work properly (fixed as per this question of mine).

I'd say it's exactly as @TheTXI suggests - ASP.NET thinks it's supposed to be a real page name and barfs. In fact, the .config one just brings up a blank page, not even a 404.

Special treatment for the URLs https://meta.stackexchange.com/questions/tagged/.aspx and https://meta.stackexchange.com/questions/tagged/.config might fix it, as well as possibly just not allowing a period in tags. (.NET can become dot-net or something?)

0

Looks like it is attempting to process the actual tag as a page. Any way the moderators can simply remove the . from the tag?

You must log in to answer this question.

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