> > >Again: a DAV-client may want to do a GET on the output (for >> testing), while >> >a non-DAV client may want to see the source code. So *this* distinction > > >doesn't make any sense at all. > > >> There's nothing about GETSRC or Translate that would _prevent_ such a >> configuration. If the administrator wants to support that, then he >> can configure his server accordingly. > >My remark referred to "know when a GET method originates from a DAV client", >no to "GETSRC" or the Translate header. I see your point. Defining "Translate: F" would probably be better than just knowing if the client is DAV-enabled, since that tells you if the client wants the source or not. That way you could have a client that could view output or source at the same URI. Otherwise you would have to define the DAV-Enabled field to only be sent when a client wanted to GET the source view of a resource, which is a little silly. cjh --Received on Wednesday, 6 March 2002 18:07:20 UTC
This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:25 UTC