This is a discussion on Content-type text/xml causes 403 forbidden response on Apache? within the Linux Web Servers forums, part of the Web Server and Related Forums category; Hello, I was wondering if anyone can help me with the strange problem. I'm trying to do an HTTP ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hello,
I was wondering if anyone can help me with the strange problem. I'm trying to do an HTTP POST of a SOAP message to my web server which is running Apache. POST /SOAP/orderServer.php HTTP/1.0 Host: www.legalresearchassociates.com Content-Type: text/xml; charset=ISO-8859-1 Content-Length: xxxx The response I get is a 403 forbidden response. The thing I don't understand is, when I remove the Content-Type, or use another Content-Type (such as Content-Type: application/x-www-form-urlencoded), it runs fine? So, if I did the same POST without a content-type, POST /SOAP/orderServer.php HTTP/1.0 Host: www.legalresearchassociates.com Content-Length: xxxx The soap server runs fine and returns a text/xml response back to me as it is supposed to. Any help will be greatly appreciated. Thanks, Dennis |
|
|||
|
sdwang@gmail.com wrote:
> POST /SOAP/orderServer.php HTTP/1.0 What does the documentation of /SOAP/orderServer.php say? > The response I get is a 403 forbidden response. The error log is your friend. > So, if I did the same POST without a content-type, > The soap server runs fine and returns a text/xml response back to me as > it is supposed to. Sounds like a broken PHP. Now why am I not in the least surprised? -- Nick Kew |