(Java) 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>

Chilkat Java Downloads Java Libs for Windows, MacOS, Linux, Alpine Linux, Solaris Java Libs for Android

import com.chilkatsoft.*;

public class ChilkatExample {

  static {
    try {
        System.loadLibrary("chilkat");
    } catch (UnsatisfiedLinkError e) {
      System.err.println("Native code library failed to load.\n" + e);
      System.exit(1);
    }
  }

  public static void main(String argv[])
  {
    CkHttpRequest req = new CkHttpRequest();

    // The ContentType, HttpVerb, and Path properties should
    // always be explicitly set.
    req.put_HttpVerb("PROPFIND");
    req.put_Path("/container/");
    req.put_ContentType("text/xml");
    req.put_Charset("utf-8");
    req.put_SendCharset(true);

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

    CkXml xml = new CkXml();
    xml.put_Tag("propfind");
    xml.AddAttribute("xmlns:D","DAV:");
    xml.NewChild2("allprop","");

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

    // View the request that would be sent if SynchronousRequest was called:
    String requestMime = req.generateRequestText();
    System.out.println(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 SynchronousRequest
    //    is called
  }
}