tag:blogger.com,1999:blog-12191231036686609772011-04-21T14:16:33.079-07:00CHAE WANhttp://www.blogger.com/profile/12534930726658691933noreply@blogger.comBlogger31100tag:blogger.com,1999:blog-1219123103668660977.post-10026277644829335242008-05-11T05:34:00.000-07:002008-05-12T15:38:02.953-07:00<span style="font-family:verdana;">Server Error<br />"A potentially dangerous Request.Form value was detected from the client (txtMessage="Australia &amp; New Z<br />...") </span><br /><br /><span style="font-family:verdana;">This error triggered due to appearance of "<", ">" in the input and the .NET framework is throwing up an error to help prevent some script injection attacks – Request Validation.<br /></span><br /><span style="font-family:verdana;">This feature was introduced with the .NET 1.1<br />It is good practice having this validation applied to all pages but in some cases I had to disable this feature.<br /><br />There are 2 ways to do this<br /></span><br /><span style="font-family:verdana;">Disabling on a page<br />Set ValidateRequest="false"<br />Eg)<br /><br /></span><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_NHxEuA7Ik9k/SCjGmhB2qUI/AAAAAAAAAA4/cdlXWQbanHU/s1600-h/page.PNG"><img style="cursor: pointer;" src="http://3.bp.blogspot.com/_NHxEuA7Ik9k/SCjGmhB2qUI/AAAAAAAAAA4/cdlXWQbanHU/s400/page.PNG" alt="" id="BLOGGER_PHOTO_ID_5199624134802712898" border="0" /></a><br /><span style="font-family:verdana;">Disabling for you application<br />You can globally turn request validation off by adding <pages validaterequest="false"> in Web.config<br />Eg)<br /></pages></span><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_NHxEuA7Ik9k/SCjFPRB2qSI/AAAAAAAAAAo/dw-TIFMXstU/s1600-h/web_config.PNG"><img style="cursor: pointer;" src="http://2.bp.blogspot.com/_NHxEuA7Ik9k/SCjFPRB2qSI/AAAAAAAAAAo/dw-TIFMXstU/s400/web_config.PNG" alt="" id="BLOGGER_PHOTO_ID_5199622635859126562" border="0" /></a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1219123103668660977-1002627764482933524?l=chaewan.blogspot.com' alt='' /></div>CHAE WANhttp://www.blogger.com/profile/12534930726658691933noreply@blogger.com0tag:blogger.com,1999:blog-1219123103668660977.post-55121147796288781742008-05-04T15:11:00.000-07:002008-05-05T15:35:10.815-07:00<a href="http://3.bp.blogspot.com/_NHxEuA7Ik9k/SB42dZVB_0I/AAAAAAAAAAg/Xz3LhYostMo/s1600-h/outlook_NoImage.PNG"><img id="BLOGGER_PHOTO_ID_5196650898675334978" style="CURSOR: hand" alt="" src="http://3.bp.blogspot.com/_NHxEuA7Ik9k/SB42dZVB_0I/AAAAAAAAAAg/Xz3LhYostMo/s320/outlook_NoImage.PNG" border="0" /></a><br /><br />There's a quick workaround for broken images on the Outlook.<br /><br />This is not the permanant fix but it helped me to release some of daily frustration quickly :)<br /><br /><br />Go to Registry editor and Remove "OutlookSecureTempFolder" Key at HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security<br /><br />As I mentioned, this is only temporary solution. This key will be regenerated periodically so need to repeat deleting as needed.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1219123103668660977-5512114779628878174?l=chaewan.blogspot.com' alt='' /></div>CHAE WANhttp://www.blogger.com/profile/12534930726658691933noreply@blogger.com1tag:blogger.com,1999:blog-1219123103668660977.post-84872773130125707052008-05-04T14:54:00.001-07:002008-05-04T14:58:13.918-07:00Hi all<br />Please feel free to look around.<br /><br />WAN<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1219123103668660977-8487277313012570705?l=chaewan.blogspot.com' alt='' /></div>CHAE WANhttp://www.blogger.com/profile/12534930726658691933noreply@blogger.com0