|
Home > Archive > IIS Server > January 2004 > URL Structure on HTTP 1.0 POST caused 405 Error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
URL Structure on HTTP 1.0 POST caused 405 Error
|
|
| Simon.Temple@nospam.com 2004-01-24, 1:44 am |
| The following does not generate an error when posting to Apache/Tomcat
POST.http://host:80/OTR/AS2/oq-2/or-MDN_HTTP/phdr/nowait HTTP/1.0
However, it generates an error when posting to IIS 5
HTTP/1.1.405.Method.not.allowed
If I change the URL I do NOT get the error:
POST /OTR/AS2/oq-2/or-MDN_HTTP/phdr/nowait HTTP/1.0
Can someone explain why?
TIA
SimonT
| |
| David Wang [Msft] 2004-01-24, 1:44 am |
| Which portion of the below URL is actually configured to be executable by
IIS?
I have no problems using absolute nor relative URL to POST on IIS5 -- but
I'm using a known executable ISAPI extension while you're using either a
default document, *-scriptmap, or ISAPI Filter -- all of which can alter IIS
behavior, so I'm asking you how you have it configured.
Some configurations may not work on IIS5 (such as POST to a default document
returns a 405 regardless if the default document can accept a POST).
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<Simon.Temple@nospam.com> wrote in message
news:3IcNb.23$aM2.4@newreader.ukcore.bt.net...
The following does not generate an error when posting to Apache/Tomcat
POST.http://host:80/OTR/AS2/oq-2/or-MDN_HTTP/phdr/nowait HTTP/1.0
However, it generates an error when posting to IIS 5
HTTP/1.1.405.Method.not.allowed
If I change the URL I do NOT get the error:
POST /OTR/AS2/oq-2/or-MDN_HTTP/phdr/nowait HTTP/1.0
Can someone explain why?
TIA
SimonT
| |
| Simon.Temple@saaconsultants.com 2004-01-24, 1:45 am |
| We are using the Tomcat redirector which is configured acording to the
details here:
http://jakarta.apache.org/tomcat/to...-iis-howto.html
In brief...
How does it work?
1. The IIS-Tomcat redirector is an IIS plugin (filter + extension),
IIS loads the redirector plugin and calls its filter function for each
in-coming request.
2. The filter then tests the request URL against a list of URI-paths
held inside uriworkermap.properties, If the current request matches one of
the entries in the list of URI-paths, the filter transfers the request to
the extension.
3. The extension collects the request parameters and forwards them to
the appropriate worker using the ajp1X protocol.
4. The extension collects the response from the worker and returns it
to the browser.
Regards
Simon Temple
| |
| David Wang [Msft] 2004-01-24, 1:46 am |
| Ah, you're talking about an ISAPI Filter and ISAPI Extension (in the form of
Tocmat) that is mutating the URL internally. So, I will not be able to
exactly explain why you get 405 in your situation. Tomcat will be mutating
the URL internally, and I do not know what URL it is using -- next to
telling you that a POST to a default document, even if considered dynamic,
will result in a 405 and is probably at the bottom of your question
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<Simon.Temple@saaconsultants.com> wrote in message
news:1QzNb.26$aM2.17@newreader.ukcore.bt.net...
We are using the Tomcat redirector which is configured acording to the
details here:
http://jakarta.apache.org/tomcat/to...-iis-howto.html
In brief...
How does it work?
1. The IIS-Tomcat redirector is an IIS plugin (filter + extension),
IIS loads the redirector plugin and calls its filter function for each
in-coming request.
2. The filter then tests the request URL against a list of URI-paths
held inside uriworkermap.properties, If the current request matches one of
the entries in the list of URI-paths, the filter transfers the request to
the extension.
3. The extension collects the request parameters and forwards them to
the appropriate worker using the ajp1X protocol.
4. The extension collects the response from the worker and returns it
to the browser.
Regards
Simon Temple
|
|
|
|
|