4744Re: [rest-discuss] REST and the design of HTTP methods
- Jan 1, 2005Julian Reschke wrote:
>Let's stick with aDoes anyone happen to know why the functionality of PROPFIND has not
>very simple example such as:
>HEAD /foo HTTP/1.1
>PROPFIND /foo HTTP/1.1
>At least in this case, PROPFIND doesn't seem to be more than a different
>way of getting the same information.
simply been enabled by
the definition of a set of additional headers, e.g.
HEAD /foo HTTP/1.1
DAV-GetProps: ContentType; ContentLength
Or would this use of headers be unRESTful anyhow?
>So is your concern about cases such as custom properties on a resource?--
>Best regards, Julian
Consultant & Programmer
- << Previous post in topic Next post in topic >>