Rust

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>

Rust

let req = chilkat::HttpRequest::new();

// The ContentType, HttpVerb, and Path properties should
// always be explicitly set.
req.set_http_verb("PROPFIND");
req.set_path("/container/");
req.set_content_type("text/xml");
req.set_charset("utf-8");
req.set_send_charset(true);

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

let xml = chilkat::Xml::new();
xml.set_tag("propfind");
let _ = xml.add_attribute("xmlns:D", "DAV:");
xml.new_child2("allprop", "");

let _ = req.load_body_from_string(&xml.get_xml().unwrap_or_default(), "utf-8");

// View the request that would be sent if HttpSReq was called:
let request_mime = req.generate_request_text().unwrap_or_default();
println!("{}", request_mime);

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