RE: Translate (was RE: DAV-Enabled field (was RE: A case for GETSRC))

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of CJ Holmes
> Sent: Wednesday, March 06, 2002 8:32 PM
> To: DAV
> Subject: RE: Translate (was RE: DAV-Enabled field (was RE: A case for
> GETSRC))
>
>
> >  > From: w3c-dist-auth-request@w3.org
> >>  [mailto:w3c-dist-auth-request@w3.org]On Behalf Of CJ Holmes
> >>  Sent: Wednesday, March 06, 2002 8:09 PM
> >>  To: DAV
> >>  Subject: RE: Translate (was RE: DAV-Enabled field (was RE: A case for
> >>  GETSRC))
> >>  ...
> >>	- have a definitive way to know when a client expects the source or
> >>	- know when a GET method originates from a DAV client
> >
> >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.

Received on Wednesday, 6 March 2002 15:54:16 UTC