Node.js

HTTP Verb - How to use any Verb (GET, PUT, POST, DELETE, PROPFIND, etc.)

The HttpVerb property may be set to anything. Typically, it is set to the common/standard HTTP verbs such as GET, POST, PUT, DELETE, etc. It can be set to anything, including custom verbs that only have meaning to your particular server-side application.

This example demonstrates how to compose an HTTP request using the PROPFIND verb, which is something one might use with a WebDAV request.

This example composes the following HTTP request:

   PROPFIND  /container/ HTTP/1.1
   Host: www.foo.bar
   Depth: 1
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propfind xmlns:D="DAV:">
     <D:allprop/>
   </D:propfind>

Node.js

NODEJS_PRELUDE

function chilkatExample() {

    var req = new chilkat.HttpRequest();

    //  The ContentType, HttpVerb, and Path properties should
    //  always be explicitly set.
    req.HttpVerb = "PROPFIND";
    req.Path = "/container/";
    req.ContentType = "text/xml";
    req.Charset = "utf-8";
    req.SendCharset = true;

    req.AddHeader("Depth","1");

    var xml = new chilkat.Xml();
    xml.Tag = "propfind";
    xml.AddAttribute("xmlns:D","DAV:");
    xml.NewChild2("allprop","");

    req.LoadBodyFromString(xml.GetXml(),"utf-8");

    //  View the request that would be sent if HttpSReq was called:
    var requestMime = req.GenerateRequestText();
    console.log(requestMime);

    //  A few important comments about the HTTP request that is generated:
    //  
    //  1) The Content-Length header is automatically generated based on the actual length of the MIME message
    //     that follows the intial (topmost) MIME header.
    //  2) The HOST header will automatically get filled in with the actual domain when HttpSReq
    //     is called.

}

chilkatExample();