W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2001

RE: SOAP/XML Protocol and filtering, etc.

From: David E. Cleary <davec@progress.com>
Date: Tue, 8 May 2001 11:45:19 -0400
To: "Keith Moore" <moore@cs.utk.edu>, "Dick Brooks" <dick@8760.com>
Cc: <xml-dist-app@w3.org>
Message-ID: <NDBBIOBPAGDGFJAHFCGGMENGCGAA.davec@progress.com>
> it breaks compatibility with HTTP, it forces SOAP implementations
> to depend
> on non-portable features of HTTP client libraries and proxies, it is not
> portable across SOAP substrates, it is not reliable as a
> filtering mechanism
> (meaning it's inherently insecure), and it doesn't work with encryption.

How does is break HTTP if HTTP 1.1 explicitly allows entity extension
headers and contains explicit rules on how they should be handled? Saying
SOAPAction breaks HTTP is a red herring. It does no such thing.
Received on Tuesday, 8 May 2001 11:49:53 GMT

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