Browser back button triggers previous post action in .NET webform application – solved

Recently while working on one of my .NET application I was stuck in a strange problem. I created a button and its click event to insert some entry in database and at the end of this action I used below statement to redirect the page for next step.

Response.Write("<script>top.location="next step page url";</script>");

Note: I used this method to redirect the page because I was doing it in an iframe and wanted to redirect parent page after this step is completed and next step is started. Keep on reading

Rules to avoid 404 error on WordPress form submit

There are some rules that are to be kept in mind while creating form in wordpress. If you won’t follow those rules then you will get 404 page on form submit:

  1. Name Field’s name should not be name, e.g : <input type=”text” name=”name” value=”” /> is wrong, because by default wordpress use name field to identify comment submission. Don’t use name as name of input field. Write another name such as <input name=”custom_name” type=”text” value=”” />
  2. Email Field’s name also should not be email, e.g : <input name=”email” type=”text” value=”” /> is wrong, because by default wordpress use email field to identify comment submission. Don’t use name as email of input field. Write another name such as <input name=”custom_email” type=”text” value=”” />
  3. Similarly don’t keep name of any input field same as custom post type slug. For example if you have a post type testimonials then don’t use field’s name as testimonials.

Keeping in mind these points you can avoid 404 page error on form submission. Keep on reading

Solution : Cross domain policy issue while calling SOAP service from your application

Some days back I was trying to call a .net SOAP web service from my Silverlight application. This was my first attempt to call a SOAP service from a Silverlight application and I saw this error

An error occurred while trying to make a request to URI ‘’. This could be due to attempting to access a service in a cross-domain way without a proper cross-domain policy in place, or a policy that is unsuitable for SOAP services. You may need to contact the owner of the service to publish a cross-domain policy file and to ensure it allows SOAP-related HTTP headers to be sent. This error may also be caused by using internal types in the web service proxy without using the InternalsVisibleToAttribute attribute. Please see the inner exception for more details. Keep on reading