Why MKCOL/PUT can't automatically create ancestor collections? from Steve K Speicher on 2001-03-23 (w3c-dist-auth@w3.org from January to March 2001)

From: Steve K Speicher <sspeiche@us.ibm.com>
Date: Fri, 23 Mar 2001 10:42:48 -0500
To: w3c-dist-auth@w3.org
Message-ID: <OF63EDD4ED.C864DEA6-ON05256A18.00559686@raleigh.ibm.com>

I understand that in RFC2518 that it clearly states that for MKCOL "..all
ancestors MUST already exist, or the method MUST fail..."

Why is this?  I can't find the rationale for not allowing the server to
automatically create ancestor collections if needed for PUT/MKCOL request
and return "201 Created".  Just wasn't sure why this is a MUST requirement
instead of a SHOULD, MAY, ...

Thanks,
Steve

Received on Friday, 23 March 2001 10:41:41 UTC