default page redirect when go back home page.
-
when I go back home , the default.aspx has also written within domain name. for example:- http://www.domaindname.com/default.aspx how to remove default.aspx to the domain name.
-
when I go back home , the default.aspx has also written within domain name. for example:- http://www.domaindname.com/default.aspx how to remove default.aspx to the domain name.
Why do you want to? People can still type in http://www.domainname.com/ and it works, right? Who cares if default.aspx gets added on? You do have to load a page.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
Why do you want to? People can still type in http://www.domainname.com/ and it works, right? Who cares if default.aspx gets added on? You do have to load a page.
There are only 10 types of people in the world, those who understand binary and those who don't.
I mean to say for example when I open asp.net c# website in local host the Default.apx page is also written within local host how to remove Default.aspx from the local host http://localhost:50050/Default.aspx in above line Default.aspx remove the main page.
-
Why do you want to? People can still type in http://www.domainname.com/ and it works, right? Who cares if default.aspx gets added on? You do have to load a page.
There are only 10 types of people in the world, those who understand binary and those who don't.
I care. It is plain ugly. In this case there is no use in having two URI's pointing to the same resource. When people can, they will keep links around to the URI including the aspx bit. Which means that all those links go broken should I change the default to index or whatever. Having the default.aspx bit reveals details about the implementation that are totally irrelevant to visitors. And those details do not serve any purpose other than increasing the burden of changing the technology stack implementing a site and that means increasing the lock-in with that technology (in other words: increasing the inertia with regard to changing it). Pretty url's do not exist for the sole reason of being pretty...
-
I care. It is plain ugly. In this case there is no use in having two URI's pointing to the same resource. When people can, they will keep links around to the URI including the aspx bit. Which means that all those links go broken should I change the default to index or whatever. Having the default.aspx bit reveals details about the implementation that are totally irrelevant to visitors. And those details do not serve any purpose other than increasing the burden of changing the technology stack implementing a site and that means increasing the lock-in with that technology (in other words: increasing the inertia with regard to changing it). Pretty url's do not exist for the sole reason of being pretty...