The Whacks behave differently, unless you give them some action.
Had an interesting situation where utilizing http://websitename/ behaved differently than http://websitename/default.aspx even though the default.aspx page was being used in both instances. I was using a third party ( infragistics ) grid that was depending on a client script to sort. When I sorted the page from http://websitename/ it failed, gave me an error stating ‘instance not found’ in the javascript. When I sorted from http://websitename/default.aspx it worked without a hitch.
At first I thought it was a cacheing issue…that my scripts weren’t being downloaded on even a hard refresh. But such was not the case. After some deliberation I turned to senior developer Chris. He thought for a while and eventually told me to add an action property in the form tag like thus:
<form id="form1" action="default.aspx" runat="server">
This worked. It enabled the scripts to find default.aspx and utilize the page properties. I asked for an explanation. Developer Chris said it had something to do with the new IIS 7 and how it has some feature which enables the whacks (/) to behave differently…and to change this behavior would require some add-in on this IIS console.
If you view the source of a page and look at the action property it will usually be action=”” which isn’t helpful for a script looking for it. So by specifying the action you can leave the whacks as they are.
