| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 10:18:30 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:28:47 GMT
cache-control: max-age=2592000, public
expires: Sun, 09 Nov 2025 10:18:30 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c55fbdd9eed86d
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=Eoa0BxMeCbKTYobvQbptQeEvUGWDlvYmwc3GXG.fHyU-1760091510-1.0.1.1-fEWl8AKPx9P.QUpgUIrz7.8PoHy2anIkU52gU2QfnBcYWikGKOswq0PgagXXYl_4wdPF8qpvsVkmrsnEG9bv0WXumeiQrtGO4sbiLFQDY.U; path=/; expires=Fri, 10-Oct-25 10:48:30 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c55fbdd9eed86d-BLR
alt-svc: h3=":443"; ma=86400
Duplicate headers at the ultimate receiver (SOAP, substantive) from Jonathan Marsh on 2005-04-12 (public-ws-addressing-comments@w3.org from April 2005)
Duplicate headers at the ultimate receiver (SOAP, substantive)
- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Tue, 12 Apr 2005 14:21:07 -0700
- To: <public-ws-addressing-comments@w3.org>
- Message-ID: <7DA77BF2392448449D094BCEF67569A507280F87@RED-MSG-30.redmond.corp.microsoft.com>
We have agreed that it is acceptable for a message to contain duplicate WSA headers, as long as they are targeted differently. To improve interoperability, we should clarify what happens when duplicate headers targeted to the ultimate recipient are inserted in a message: 'A message MUST not contain more than one wsa:To, wsa:ReplyTo, wsa:FaultTo, wsa:Action, or wsa:MessageID header targeted to the ultimate receiver. A recipient MUST generate a wsa:InvalidMessageAddressingProperty fault in this case.'
Received on Tuesday, 12 April 2005 21:21:20 UTC