I made a mistake in my message to the list. I was reading from the JAX RPC spec from Sun, which does require HTTP 1.1.
That leaves me with the original problem of trying to use Apache SOAP as a client to make a request over HTTP/1.1 protocol. I'll look into the constants file as was previously posted as a reply message. And then I'll post my findings here. -Frank Re: HTTP 1.1 Protocol for SOAP requests: /*Here is the relevant text for HTTP Extensions from W3C*/ http://www.w3.org/TR/SOAP/#_Toc478383530 A SOAP message MAY be used together with the HTTP Extension Framework [6] in order to identify the presence and intent of a SOAP HTTP request. Whether to use the Extension Framework or plain HTTP is a question of policy and capability of the communicating parties. Clients can force the use of the HTTP Extension Framework by using a mandatory extension declaration and the "M-" HTTP method name prefix. Servers can force the use of the HTTP Extension Framework by using the 510 "Not Extended" HTTP status code. That is, using one extra round trip, either party can detect the policy of the other party and act accordingly. /*Thus the Server can DEMAND the HTTP Extension Framework request from client*/ /*Here is the relevant RFC (2774) from W3C.*/ The proposal uses features in HTTP/1.1 but is compatible with HTTP/1.0 applications in such a way that extended applications can coexist with existing HTTP applications. Applications implementing this proposal MUST be based on HTTP/1.1 (or later versions of HTTP). /*Information courtesy of 6] H. Nielsen, P. Leach, S. Lawrence, "An HTTP Extension Framework", RFC 2774, Microsoft, Microsoft, Agranat Systems */ Martin Gainty ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Laconia Data Systems (LDS) is proprietary to the company. It is confidential, legally privileged and protected by law. LDS does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of LDS. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. LDS can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. _______________________________________________ >From: Sam Ruby >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: Re: HTTP 1.1 Protocol for Requests >Date: Tue, 18 Jun 2002 03:22:26 -0400 >MIME-Version: 1.0 >Received: from [63.251.56.142] by hotmail.com (3.2) with ESMTP id MHotMailBED82B1D000E4136E84B3FFB388EC86F0; Tue, 18 Jun 2002 00:24:13 -0700 >Received: (qmail 21206 invoked by uid 500); 18 Jun 2002 07:23:43 -0000 >Received: (qmail 21196 invoked from network); 18 Jun 2002 07:23:43 -0000 >Received: from scandium.sabren.com (209.61.155.99) by daedalus.apache.org with SMTP; 18 Jun 2002 07:23:43 -0000 >Received: from us.ibm.com (rdu57-27-066.nc.rr.com [66.57.27.66])(authenticated (0 bits))by scandium.sabren.com (8.11.6/8.11.6) with ESMTP id g5I7Nt303609for ; Tue, 18 Jun 2002 03:23:55 -0400 >From soap-user-return-14011-mgainty Tue, 18 Jun 2002 00:24:48 -0700 >Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm >Precedence: bulk >list-help: >list-unsubscribe: >list-post: >Delivered-To: mailing list [EMAIL PROTECTED] >Message-ID: <[EMAIL PROTECTED]> >User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 >X-Accept-Language: en-us, en >References: >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > >Frank Cohen wrote: > >>The SOAP 1.1 specification says that HTTP/1.1 is required. >> >> > >It does? Can you provide a reference? > >Apache SOAP interoperates with a large number of other SOAP >stacks... >see http://www.apache.org/~rubys/ApacheClientInterop.html > >- Sam Ruby > Send and receive Hotmail on your mobile device: Click Here <http://g.msn.com/1HM505401/45>
