| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 04:07:23 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:20:29 GMT
cache-control: max-age=2592000, public
expires: Sun, 09 Nov 2025 09:16:14 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c5048cf8664bc2
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=lLQsfARwS2dMMgcbpR.eDdqBkIIEeWJWrZSxEdtjf5w-1760155643-1.0.1.1-LrLQ8LpzRA8veGMSy_14AHqVkZ_WpEmPTO76MPKbBFlRVdS8TAJ6mpILO6sVZEvNUU_3Tan_z.xVWPjLRyUhLjRYlTfgtrQb_SJerx0cctc; path=/; expires=Sat, 11-Oct-25 04:37:23 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cb7d7cba9f5ace-BLR
alt-svc: h3=":443"; ma=86400
BIND and HTTP status codes from Julian Reschke on 2008-09-26 (w3c-dist-auth@w3.org from July to September 2008)
BIND and HTTP status codes
- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 26 Sep 2008 14:44:39 +0200
- To: WebDAV <w3c-dist-auth@w3.org>
- Message-ID: <48DCD937.8070109@gmx.de>
Hi, while implementing WebDAV BIND in Jackrabbit [1] (the Apache Java Content Repository Reference Implementation), my colleague Manfred Baedke noticed that the spec currently micro-manages HTTP status codes: for instance, for a successful BIND it requires status codes of 200 or 201, while - from an HTTP point of view - a 204 should be acceptable as well. Proposal: rephrase the text so that other success codes are acceptable as well, or remove the normative language completely, point to RFC2616, and rely on examples. BR, Julian [1] <https://issues.apache.org/jira/browse/JCR-1733>
Received on Friday, 26 September 2008 12:45:23 UTC