@techreport{ietf-http-options-02,
    number =    {draft-ietf-http-options-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-http-options/02/},
    author =    {Jeffrey Mogul and John W. Cohen M.A.},
    title =     {{Specification of HTTP/1.1 OPTIONS messages}},
    pagetotal = 12,
    year =      1997,
    month =     aug,
    day =       29,
    abstract =  {RFC2068 defined a new OPTIONS method for HTTP/1.1. The purpose of OPTIONS is to allow a 'client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.' However, RFC2068 did not defined a specific syntax for using OPTIONS to make such a determination. This proposal clarifies the original specification of OPTIONS, adds several new HTTP message headers to provide syntactic support for OPTIONS, and establishes new IANA registries to avoid namespace conflicts.},
}