| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 10:17:40 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: Sun, 09 Nov 2025 10:17:40 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c55e87a9fdcf00
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=FEchq3OYK9XWWMXFM2uiM0xdGo9Bl5dnUHVdaSwjyFM-1760091460-1.0.1.1-n.WxjuRbJx9E938LmdY6ANbynfQwit_Ug4rJat5eUQ5rtefU.rnb_rfclX9Kg4Op9o3FdXzl.VMjY3ZhKkeRUASCy_UkQXwO46C0iPNwG1Y; path=/; expires=Fri, 10-Oct-25 10:47:40 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c55e87a9fdcf00-BLR
alt-svc: h3=":443"; ma=86400
LC Comment: (editorial) Processors unconstrained in the face of non-compliant messages. from David Hull on 2005-05-05 (public-ws-addressing-comments@w3.org from May 2005)
LC Comment: (editorial) Processors unconstrained in the face of non-compliant messages.
- From: David Hull <dmh@tibco.com>
- Date: Thu, 05 May 2005 17:47:57 -0400
- To: public-ws-addressing-comments@w3.org
- Message-id: <427A948D.9030604@tibco.com>
The intent of the core (as I understand it) is that processors are free to do as they like when sent non-compliant messages. In particular, this allows them to handle plain HTTP requests as they always would have. If so, this should be made explicit in section 3.2 for the sake of clarity, by including a statement to the effect that "This specification places no constraints on the processing of non-compliant messages."
Received on Thursday, 5 May 2005 21:48:02 UTC