Xbase++

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>

Xbase++

LOCAL oReq
LOCAL oXml
LOCAL cRequestMime

oReq := CreateObject("Chilkat.HttpRequest")

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

oReq:AddHeader("Depth", "1")

oXml := CreateObject("Chilkat.Xml")
oXml:Tag := "propfind"
oXml:AddAttribute("xmlns:D", "DAV:")
oXml:NewChild2("allprop", "")

oReq:LoadBodyFromString(oXml:GetXml(), "utf-8")

//  View the request that would be sent if HttpSReq was called:
cRequestMime := oReq:GenerateRequestText()
? cRequestMime

//  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.

oReq:destroy()
oXml:destroy()