Possible Duplicate:
Please prevent creation of tags that could trigger the IIS file extension filter

How do I display questions related for the following tags ?

My problem is that in none of the well known browsers (Firefox, IE or Chrome) I have tried this on I wasn't able to display related questions for them (because of some kind of security block or expected dll file ?)

P.S. I did that because I've been looking for some unanswered question related to Scintilla (Scilexer.dll) but here I get stucked:

enter image description here

So far I found this at tags; the other file or extension tags like for instance , works fine.

share|improve this question
So it would be great if the links from the tags would end by the /. –  TLama Jun 23 '12 at 19:59
add comment

marked as duplicate by Geoff Dalgas Sep 11 '12 at 23:59


2 Answers

up vote 1 down vote accepted

I don't know what was causing the problem (it happens for me too), but there is a very simple workaround.

If you have a tag URL such as http://stackoverflow.com/questions/tagged/scilexer.dll simply add a slash to the end of the URL, http://stackoverflow.com/questions/tagged/scilexer.dll/

In Firefox, Chrome, and Safari, at least, this will make the browser interpret the URL as a folder rather than a file, and so it will display correctly. I have not tested it in IE or Opera.

share|improve this answer
D'oh, that's what I haven't think about. Thanks! +1, accept and bounty (in 22 hours) is yours ;-) However it's interesting that for the other extensions those browsers works. They evidently don't like *.dll. –  TLama Jun 23 '12 at 19:57
add comment

There's a famous bug about URL's ending in .dll in Microsoft's web server, no?

share|improve this answer
Might be, I haven't met this before (because as I remember I've never downloaded standalone dll file), but is that really the reason why Firefox and Chrome (at least those I've tried) protects against that ? One thing I would suggest in this case is to add the slash to the end of the links going from the tags. Thanks for the post anyway, but it feels more like a comment to me ;-) –  TLama Jun 23 '12 at 20:18
It's on the server side, not the client side. –  Rosinante Jun 23 '12 at 20:21
Ah, I see what you mean. So it's not a browsers problem but the Stack's server side. Sorry, I'm really lame to this stuff, I'm a desktop app maniac, but good to know this :-) –  TLama Jun 23 '12 at 20:24
add comment

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