W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

Re: Issue 133, and permitting no body

From: Yves Lafon <ylafon@w3.org>
Date: Fri, 1 Feb 2002 18:04:29 +0100 (MET)
To: Mark Baker <distobj@acm.org>
cc: Noah Mendelsohn <noah_mendelsohn@us.ibm.com>, <xml-dist-app@w3.org>
Message-ID: <Pine.GSO.4.44.0202011519340.3607-100000@tarantula.inria.fr>
On Fri, 1 Feb 2002, Mark Baker wrote:

> Yves,
>
> I'm not sure I follow.  Where does the urlencoding of the SOAP message
> come in, in this example?

Hum, that's the problem when you forget some while lines in an email.
urlencoding of SOAP message is useful if you know in advance that the
method called will be idempotent, and a way to call it
ex: http://www.example.com/stockquote?soap=<urlencoded enveloppe>.
or  http://www.example.com/stockquote;soap=<urlencoded enveloppe>

The problem is that some deployed proxies or server will disallow too long
URIs.
Should we define a preferred way to encode in the URI (using soap= as an
argument for example) or should it be handled by the description of the
service?

The POST -> 303 GET is another story :)

-- 
Yves Lafon - W3C
"Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Friday, 1 February 2002 12:04:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT