When clicking on a question tagged .aspx, the site produces a 'Page Not Found' error.
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.
Also note this only happens with ASP.NET related-extensions (e.g.
.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/.config might fix it, as well as possibly just not allowing a period in tags. (
.NET can become
dot-net or something?)
Looks like it is attempting to process the actual tag as a page. Any way the moderators can simply remove the . from the tag?