Overthere
asked on
Http ERROR 404 AND POST VERB
I am using Visual Studio Express 2010. In my site, I have several folders and all my pages can find the correct images and etc.
However, I have a page that contains a form and below is the line of coding:
<form action="docs/validate.asp" method="post" name="Form1" onSubmit="return checkfields();">
But I recieve this error and don't understand why.
The HTTP verb POST used to access path '/MyNuWeb/docs/validate.as p' is not allowed.
Why am I receiving this? The page that contains the form and calling 'validate.asp' was originaly developed in Dreamweaver MX 2003.
However, I have a page that contains a form and below is the line of coding:
<form action="docs/validate.asp"
But I recieve this error and don't understand why.
The HTTP verb POST used to access path '/MyNuWeb/docs/validate.as
Why am I receiving this? The page that contains the form and calling 'validate.asp' was originaly developed in Dreamweaver MX 2003.
First thing to try is to change "POST" to "GET" in the <form> tag, and hope that the CGI script will accept either. If that works, you're good. If not, we need to figure out how to enable POSTs for your website.
Do you have access to your web server or is hosted elsewhere?
If you can and it's IIS then go to the config in IIS, go to the asp extension and ensure POST is listed
If you can and it's IIS then go to the config in IIS, go to the asp extension and ensure POST is listed
ASKER
I am using my local machine as sever and to develope upon. I have IIS 7 and I have looked in IIS from the control panel and can't figure out where to go to do so. Could you provide me with more help?
ASKER
I changed from "post" to "get" and received the same error!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried both things and it was still a no go. I ended up recreating the page as a aspx page and it works. Thanks anyway for helping. It's going to be a long night...sigh