Home/ Questions/Q 7588913
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T20:02:46+00:00

I am receiving an error that states: The HTTP verb POST used to access

  • 0

I am receiving an error that states: “The HTTP verb POST used to access path ‘[my path]’ is not allowed.”.

The error is being caused by the fact that I am implementing an HTML form element that uses the POST method and does not explicitly define an .aspx page in its ACTION parameter.

For example:

<form action="" method="post">
  <input type="submit" />
</form>

The HTML above is on a file at “/foo/default.aspx”.

Now, if the user points the URL to the root directory “foo” without specifying the aspx file (i.e. “http://localhost/foo&#8221;) and then submits the form, the error “The HTTP verb POST used to access path ‘/foo’ is not allowed.” will be thrown.

However, if the user goes to “http://localhost/foo/default.aspx&#8221; and then submits the form, all goes well (even if the ACTION parameter is left empty).

Note: If I explicitly add the name of the .aspx (default.aspx) page to the ACTION parameter, no errors are thrown. So the example below works fine regardless if the user defines the name of the file in the URL or not.

<form action="default.aspx" method="post">
  <input type="submit" />
</form>

I was curious as to why the error was being thrown, so I read a Microsoft KB that states

This problem occurs because a client
makes an HTTP request by sending the
POST method to a static HTML page.
Static HTML pages do not support the
POST method.

I suppose the core of the explanation makes sense, however in my case, my form is not being sent to a static html page – it’s being sent to the same page that the html form lives on (default.aspx)… this is implicit to an ACTION param that is left empty.

Is it possible to configure IIS (or otherwise) that will allow us to do form POSTing and keep the ACTION param empty?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s been a year since initially experienced this error and thought I should add to this post that I am no longer receiving the error.

    I don’t know what fixed the problem, but my guess is that the error has gone away due to some Windows Update that has been implemented on my dev machine within the year.

    One thing I noticed in the IIS 7 settings is that the “ISAPI.DLL” (in the “Handler Mappings” section) is disabled. I can’t figure out how to “enable” it in order to try to reproduce the problem to show that the ISAPI.DLL is causing (or related) to the problem.

    Anyway, the I am unable to reproduce this error that occurs when I leave the “action” attribute blank in an HTML Form tag. So, my guess is that there is an IIS and/or .NET Framework update that implicitly or explicitly fixes the error mentioned in the OP.

    • 0