One difference I see is that Apache SOAP 2.3.1 includes the port in the HTTP Host 
header.  What bothers me is that it asks for port 8000, yet the response message says 
the server is at 7778.  Is 7778 an admin port or something?

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message ----- 
From: "Dragos Vilcu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 20, 2004 2:21 AM
Subject: Re: SOAP CHARSET UTF-8


>The client payload you show below looks like SOAP 2.3.1, which is good.  It
should be able to properly encode characters as UTF-8, and as you see, it
>specifies that charset in the Content-Type header.
>The error response from the server is very generic.  Are you certain that
the URL is correct?  If you point your browser to
>http://dragos:8000/soap/servlet/soaprouter, what do you see?  If Apache
SOAP is configured to handle that URL, your browser should show a page with
the >message "Sorry, I don't speak via HTTP GET- you have to use HTTP POST
to talk to me."



The URL is correct.
Case 1) When I use SOAP 2.3.1 for Client it didn't work.

Case 2) When I use  "soap.jar" provided by  Oracle (iAS v1.0.2.2.) for
client (i think that the version of SOAP is 1.1 ?), it works fine with the
same url.
The only thing that it didn't work in this case is the transmision of
specific Romanian characters like 'ş', 'ţ', 'ă', 'î', 'â'.
This is what is really bothering me, and I don't know how to fix it.


Case 1)

//The call looks now like this :

POST /soap/servlet/soaprouter HTTP/1.0
Host: dragos:8000
Content-Type: text/xml; charset=utf-8
Content-Length: 1835
SOAPAction: "urn:wsrpp"
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

.......

but I encounter the following error from the server :

HTTP/1.1 400 Bad Request
Date: Thu, 19 Feb 2004 15:32:13 GMT
Server: Oracle HTTP Server Powered by Apache/1.3.22 (Win32) mod_ssl/2.8.5
OpenSSL/0.9.6b mod_fastcgi/2.2.12 mod_oprocmgr/1.0 mod_perl/1.25
Set-Cookie:
JServSessionIdsoap=mk9dp648u1.n79vnQXN/A5NnlbJnBeIokTOp3DGpQbvp6vJqReUb38LbK
--; path=/
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD><BODY>
<H1>Bad Request</H1>
Your browser sent a request that this server could not understand.<P>
<HR>
<ADDRESS>Oracle HTTP Server Powered by Apache/1.3.22 Server at
dragos.asesoft.intl Port 7778</ADDRESS>
</BODY></HTML>
....................................................................

Case 2)
//The call looks now like this :

POST /soap/servlet/soaprouter HTTP/1.0
Host: dragos
content-type: text/xml
soapaction: "urn:wsrpp"
user-agent: Oracle-Soap-Client/1.0 HTTP/1.0
Content-Length: 1773
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
<SOAP-ENV:Body>


//Response
HTTP/1.1 200 OK
Date: Fri, 20 Feb 2004 06:51:51 GMT
Server: Oracle HTTP Server Powered by Apache/1.3.22 (Win32) mod_ssl/2.8.5
OpenSSL/0.9.6b mod_fastcgi/2.2.12 mod_oprocmgr/1.0 mod_perl/1.25
Set-Cookie:
JServSessionIdsoap=4lthv6pj71.n79vnQXN/A5NnlbJnBeIokTOp3DGpQbvp6vJqReUax0Mbe
--; path=/
Content-Length: 513
Connection: close
Content-Type: text/xml; charset=UTF-8
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
<SOAP-ENV:Body>



Reply via email to