How to enable post method on Server 2003 IIS 6? HTTP Error 405

iis-6windows-server-2003

I'm programming an Android application that read an XML file that sits on my server.
I'm using POST method in order to simply get the content of the XML (or any other file for that matter) using simple POST and RESPONSE methods.

// java code
HttpPost httpPost = new HttpPost(XML_FILE);
HttpResponse httpResponse = httpClient.execute(httpPost);
HttpEntity httpEntity = httpResponse.getEntity();

it works fine on one of my linux servers but when I tried on my Windows 2003 IIS 6 server I get a

HTTP Error 405 – The HTTP verb used to access this page is not
allowed.
Internet Information Services (IIS)

I tried to add

<protocols>
      <add name="HttpGet"/>
      <add name="HttpPost"/>
</protocols>

to my web.config file but the results are the same.

I think the problem is that POST methods are disabled by defualt by I cant figure out how to enable them. do you think thats really is my problem? if so, how to I enable it?

Best Answer

Generally this means that you are trying to POST to a page that only has a static handler (like a .html file).

You need to ensure that your ISAPI plugin for the language you're posting to (.net or php or whatever) needs to be set up correctly and enabled.

Related Solutions

Web-server – Why does IIS refuse to serve ASP.NET content

I've run into this exact issue several times, and every time, the solution was to:

go to the Control Panel
go to the "Windows Components" area
remove IIS, let it uninstall
reboot
re-add IIS (make sure to include the ASP.NET stuff when you check off the boxes).
Run: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -I

I spent hours debugging this at a client site once, and that was the trick. Since then, every time this has happened, this was the fix.

I'm not sure what the root cause is, but we tore the IIS configuration apart once trying to figure it out, and even had Microsoft RDC'ing into the server in question for 2 or 3 hours, and they couldn't help either.

So I write it off as an undocumented bug in ASP.NET/IIS.

Iis – Server 2003 IIS Error

This problem might occur because ASP.NET limits the number of worker threads and completion port threads that a call can use to execute requests.

Typically, a call to a Web service uses one worker thread to execute the code that sends the request and one completion port thread to receive the callback from the Web service. However, if the request is redirected or requires authentication, the call may use as many as two worker and two completion port threads. Therefore, you can exhaust the managed ThreadPool when multiple Web service calls occur at the same time.

For example, suppose that the ThreadPool is limited to 10 worker threads, and all 10 worker threads are currently executing code that is waiting for a callback to execute. The callback can never execute because any work items that are queued to the ThreadPool are blocked until a thread becomes available.

Another potential source of contention is the maxconnection parameter that the System.Net namespace uses to limit the number of connections. Generally, this limit works as expected. However, if many applications try to make many requests to a single IP address at the same time, threads may have to wait for an available connection. To resolve these problems, you can tune the following parameters in your Machine.config file to best fit your situation:
* maxWorkerThreads
* minWorkerThreads
* maxIoThreads
* minFreeThreads
* minLocalRequestFreeThreads
* maxconnection
* executionTimeout
To successfully resolve these problems, do the following...

The quote's continued here... If that doesn't work, you can dig deeper with what's explained here.

Best Answer

Related Solutions

Web-server – Why does IIS refuse to serve ASP.NET content

Iis – Server 2003 IIS Error

Related Topic