Disabling HTTP Processing For Unrecognized HTTP Methods

Using this iRule has one limitation for IIS servers acting as a WebDAV distribution point with SSL Offloading on BIG-IP enabled. When SSL Offloading on BIG-IP is enabled and client uses COPY/MOVE method there is a header with name "Destination" that starts with https (because client is connecting to WebDAV with SSL). IIS does not recognises that destination because servers are running as HTTP and expecting http appended string in "Destination" header

Here are my fixed iRule:

 Works for TMOS 11.6.0+
 https://support.f5.com/csp//article/K13285

 Make this iRule to be called the last one because of the HTTP::disable
priority 700

when CLIENT_ACCEPTED
{
     Enable HTTP processing for all requests by default
    HTTP::enable
}

when HTTP_REQUEST
{
     Selectively disable HTTP processing for specific request methods
    switch [HTTP::method]
    {
        "COPY" -
        "MOVE"
        {
             Replace Destination header with http if using SSL Offloading
            if { [HTTP::header Destination] starts_with "https" }
            {
                HTTP::header replace Destination [string map -nocase {https http} [HTTP::header value Destination]]
            }

            HTTP::disable
        }
        "MKCOL" -
        "PROPPATCH"
        {
            HTTP::disable
        }
   }
}

OPTIONS should be added to the switch statement:

The Linked DevCentral Article needs to be updated to include 'OPTIONS' HTTP Request Method.

when HTTP_REQUEST {
    selectively disable HTTP processing for specific request methods
   switch [HTTP::method] {
      "MOVE" -
      "COPY" -
      "LOCK" -
      "UNLOCK" -
      "OPTIONS" -
      "PROPFIND" -
      "PROPPATCH" -
      "MKCOL" { HTTP::disable }
   }
}

How can we disable HTTP HEAD method as per PCI compliance