options revisited

From: Josh Cohen (joshco@microsoft.com)
Date: Fri, Feb 27 1998


Message-ID: <8B57882C41A0D1118F7100805F9F68B5078582@red-msg-45.dns.microsoft.com>
From: Josh Cohen <joshco@microsoft.com>
To: "'ietf-http-ext@w3.org'" <ietf-http-ext@w3.org>
Date: Fri, 27 Feb 1998 01:49:36 -0800
Subject: options revisited

I had gotten some comments from koen in the
past on the OPTIONS drafts and Ive been going
through them as well as solicitiing other
comments on how to move an OPTIONS mechanism forward.

Ill be including more comments from koen tomorrow,
but Id love to see other comments as well..

ISSUES with OPTIONS

1) [koen] Multi-node, distributed, or modular servers and proxies may
have different compliance levels depending on the individual modules.
So, if a CGI script is forked off by a server as an isolated program,
the server cant vounch for its compliance.

resolution:
 If a client asks for a server wide compliance declaration, the
server may respond on behalf of the entire server.  HOWEVER, if the
server forks off a CGI script or a module, for which it cannot vouch
for compliance to a previously declared compliance declaration, it must
indicate that.   It should indicate this by using the non-compliance
header with the 'exception' indicator.



---
Josh Cohen <josh@microsoft.com>
Program Manager IE - Networking Protocols