Loading ...
Sorry, an error occurred while loading the content.

4744Re: [rest-discuss] REST and the design of HTTP methods

Expand Messages
  • Jan Algermissen
    Jan 1, 2005
    • 0 Attachment
      Julian Reschke wrote:

      [...]

      >Let's stick with a
      >very simple example such as:
      >
      >HEAD /foo HTTP/1.1
      >Host: example.com
      >
      >vs
      >
      >PROPFIND /foo HTTP/1.1
      >Host: example.com
      >Depth: 0
      >Content-Type: application/xml
      >
      ><propfind xmlns="DAV:">
      > <prop><getcontenttype/><getcontentlength></prop>
      ></propfind>
      >
      >At least in this case, PROPFIND doesn't seem to be more than a different
      >way of getting the same information.
      >
      >
      Does anyone happen to know why the functionality of PROPFIND has not
      simply been enabled by
      the definition of a set of additional headers, e.g.

      HEAD /foo HTTP/1.1
      Host: example.com
      DAV-GetProps: ContentType; ContentLength

      ???

      Or would this use of headers be unRESTful anyhow?

      Jan


      >So is your concern about cases such as custom properties on a resource?
      >
      >Best regards, Julian
      >
      >
      >


      --
      Jan Algermissen
      Consultant & Programmer
      http://jalgermissen.com
    • Show all 25 messages in this topic