| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 07:48:42 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:28:48 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 07:48:42 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98ccc1b00c891712
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=nZ1wQcvpWrGQno_HaO1GRgIHwk_AIMKbEiIJqkF207I-1760168922-1.0.1.1-lTuPLywLaGrIAY15LCCIq85JDT8k_uUTt3pRHxFAGbkHlsHJixrospdo27Ts7.wIPKqZ2r1pHVsu2oK.ymmXLctMEcqZa8xdON2GnUOuqVQ; path=/; expires=Sat, 11-Oct-25 08:18:42 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ccc1b00c891712-BLR
alt-svc: h3=":443"; ma=86400
LC Comment:(editorial) Use of mustUnderstand=1 in example from David Hull on 2005-05-05 (public-ws-addressing-comments@w3.org from May 2005)
LC Comment:(editorial) Use of mustUnderstand=1 in example
- From: David Hull <dmh@tibco.com>
- Date: Thu, 05 May 2005 17:16:24 -0400
- To: public-ws-addressing-comments@w3.org
- Message-id: <427A8D28.3090709@tibco.com>
Examples 3-2 and 3-3 show SOAP messages with s:mustUnderstand=1 for the wsa:To header, but not for any other header. The SOAP binding says nothing about the mustUnderstand header at all. If mustUnderstand is meant to reflect that the wsa:To header is mandatory, it should be present on the wsa:Action as well, but more likely this is just an oversight and the s:mustUnderstand attribute should be removed to avoid muddying the waters.
Received on Thursday, 5 May 2005 21:16:29 UTC