I've noticed that a lot of the popular sites do a good job in hiding their file extensions.
I guess with the MVC concept, you're really not working with files but more so with views.
I get that, but what are other motivations?
I've noticed that a lot of the popular sites do a good job in hiding their file extensions.
I guess with the MVC concept, you're really not working with files but more so with views.
I get that, but what are other motivations?
Exposing file extensions can be a huge maintenance headache if you ever switch / upgrade technologies on your website. I can remember quite a few headaches when moving from Classic ASP to .NET and having a lot of .asp links both internally and exposed to search engines that needed to be changed to .aspx.
One reason is security, if someone is trying to hack your site and they can see the file extension they know straight away what the underlying technology is and therefore any known security holes in that technology. Note there are other ways of them finding this out though.
Because Cool URLs Don't Change. So if there's anything in your URL that is tied to your current technology stack, hide or eliminate it, so that when you change your technology stack, you don't have to change your URLs. Changing your URL may also cause you to lose ranking in search engines.
Push things that may change out of your URLs, aggressively.