Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 155 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

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

share|improve this question
    
Reproduced in Google Chrome (3.0.196.2). Clicking the aspx tag results in a Page Not Found error as described. – Jeff Yates Aug 4 '09 at 13:59
    
temporary solution: meta.stackexchange.com/questions/27702/… – alexandrul Oct 30 '09 at 11:37
up vote 3 down vote accepted

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.

share|improve this answer
    
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

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

share|improve this answer

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 http://meta.stackexchange.com/questions/tagged/.aspx and http://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?)

share|improve this answer

You must log in to answer this question.

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