Wish you new year 2011

Comments

Post a Comment

Popular posts from this blog

IE10 breaking changes compatibility

Microsoft feeds us. New versions they introduce gives business to developers like us :-P. IE10 release preview got released. Along with other changes to conform the browser's behavior with html standards, there were two changes which broke one old and one new applications of ours. First one: support for .htc files (very old html control files) got removed.Although we had started porting our htc into asp.net user controls, there is still a huge part still in htc. Second one: support for conditional html statements got removed. http://www.sitepoint.com/microsoft-drop-ie10-conditional-comments/ To add to this, for some reason we are still analyzing, telerik controls got some issue with working with IE10. The only option remaining was to force IE10 into emulate IE9 mode. (Although IE10 users can explicitly use the compatibiliy mode, users generally are not aware of this and raise an issue with the support team.) However, to add to our problems, IE10 wont allow htc to run...
Read more

Dirty workarouds: dirty page checking + AJAX

Dirty page checking is scenario when you have a form, user does some modifications and before hitting the save button, tries to leave the page. Enterprise web applications have a requirement to intimate the user that "there are unsaved details" and "do you really want to move away from this page". The idea of solution behind this is 1. use of window.beforeunload and 2. use of onchange to register the window.beforeunload. As setting window.beforeunload manually for each control can be timeconsuming, we need a generic solution which will work with minimal code changes. If you search for this on internet, you will find the following generic code: <script type="text/javascript"> function setDirty() { window.onbeforeunload = showNavigateAwayMessage; } function clearDirty() { window.onbeforeunload = ""; } function showNavigateAwayMessage() { return "There is some unsaved Data in this form." } function setControlChangeEvent() { if (typeo...
Read more

Security with Server.Transfer

Difference between Response.Redirect and Server.Transfer is a favorite (and common) interview question. One of the benefits of Server.Transfer is that round trip to the client browser is avoided. Recently, we were so much carried away by this advantage that we hit a security issue (and this is usually not mentioned in the interview questions listing sites :-)). We are using a custom http module for that takes care of Windows Live authentication + custom defined authorization and sends it to the asp if the user is defined as valid user for the page accessed. indexpage.aspx -> accessible to all specialpage.aspx - > accessible to only admins indexpage.aspx had a logic and redirect to specialpage.aspx on a special condition. Something went wrong in this checking and users who had no permission to specialPage.aspx were sent to it via Server.Transfer. And because we were using Server.Transfer, it directly got transferred without the httpmodule comong in between. Had we used Response.R...
Read more