- From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
- Date: Mon, 03 Aug 1998 19:20:11 -0700
- To: ccjason@us.ibm.com
- cc: w3c-dist-auth@w3.org
>I just want to recheck how Server Side Includes work so that we are doing >them is similar ways... > >Traditionally, one PUT's a *.shtml file at a specified URL and GET requests >to that URL result in the out put of executing the SSI. I wouldn't allow that. If the server is maintaining the source file under a different URL than the GET, then a PUT on the latter URL should result in an error or redirection to the source URL. The server can determine that from the URL and content of the PUT. Otherwise the author is likely to be confused about what is being authored. This is also a key issue for deployment, since older tools might be mistakenly used to modify and PUT the generated content rather than the source content. It also makes access control easier. ....Roy
Received on Monday, 3 August 1998 22:22:20 UTC