by wmorein on 6/12/09, 8:45 PM with 21 comments
by hugothefrog on 6/12/09, 9:41 PM
The filename limitation isn't the only problem. There's also a limit of 260 characters in the URL.
http://stackoverflow.com/questions/265251/asp-net-url-maxpat...
Boo-sucks if you suddenly run into that without expecting it!
by smhinsey on 6/13/09, 12:18 AM
This is not correct. When you configure an ISAPI filter in IIS, such as ASP.NET or PHP, you can choose whether or not to verify the presence of files. You can also do this via configuration for .NET HTTP handlers. Parts of ASP.NET itself rely on this feature, such as the trace.axd handler and the web resource handlers.
I don't have the option to verify that you can't create those routes, but if you can't, it's not related to that particular feature.
by Elepsis on 6/13/09, 1:55 AM
by kingsley_20 on 6/12/09, 10:39 PM
Technology may not be immune from the stubbornness of standards that no one feels inclined to change.
by rbanffy on 6/12/09, 10:20 PM
And what's the matter with the "all extensions" thing?
/me ducks and says goodbye to karma.
by monological on 6/12/09, 10:12 PM
by chanux on 6/13/09, 7:00 AM
by sarvesh on 6/12/09, 9:31 PM
by justin_vanw on 6/13/09, 1:33 AM
Astroturf should be left for the Jetson's dog to play on.