|
// ------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
// ------------------------------------------------------------------------------
#pragma warning disable CS1591,CS1573,CS0465,CS0649,CS8019,CS1570,CS1584,CS1658,CS0436,CS8981
using global::System;
using global::System.Diagnostics;
using global::System.Diagnostics.CodeAnalysis;
using global::System.Runtime.CompilerServices;
using global::System.Runtime.InteropServices;
using global::System.Runtime.Versioning;
using winmdroot = global::Windows.Win32;
namespace Windows.Win32
{
namespace Networking.HttpServer
{
/// <summary>The HTTP_VERB enumeration type defines values that are used to specify known, standard HTTP verbs in the HTTP_REQUEST structure. The majority of these known verbs are documented in RFC 2616 and RFC 2518, as indicated below.</summary>
/// <remarks>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb">Learn more about this API from docs.microsoft.com</see>.</para>
/// </remarks>
[global::System.CodeDom.Compiler.GeneratedCode("Microsoft.Windows.CsWin32", "0.3.46-beta+dd815b2b9b")]
internal enum HTTP_VERB
{
/// <summary>Not relevant for applications; used only in kernel mode.</summary>
HttpVerbUnparsed = 0,
/// <summary>Indicates that the application can examine the <b>UnknownVerbLength</b> and <b>pUnknownVerb</b> members of the <a href="https://docs.microsoft.com/previous-versions/windows/desktop/legacy/aa364545(v=vs.85)">HTTP_REQUEST</a> structure to retrieve the HTTP verb for the request. This is the case in an HTTP/1.1 request when a browser client specifies a custom verb.</summary>
HttpVerbUnknown = 1,
/// <summary>Not relevant for applications; used only in kernel mode.</summary>
HttpVerbInvalid = 2,
/// <summary>
/// <para>The OPTIONS method requests information about the communication options and requirements associated with a URI.</para>
/// <para>See page 52 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbOPTIONS = 3,
/// <summary>
/// <para>The GET method retrieves the information or entity that is identified by the URI of the Request. If that URI refers to a script or other data-producing process, it is the data produced, not the text of the script, that is returned in the response. A GET method can be made conditional or partial by including a conditional or Range header field in the request. A conditional GET requests that the entity be sent only if all conditions specified in the header are met, and a partial GET requests only part of the entity, as specified in the Range header. Both of these forms of GET can help avoid unnecessary network traffic.</para>
/// <para>See page 53 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbGET = 4,
/// <summary>
/// <para>The HEAD method is identical to GET except that the server only returns message-headers in the response, without a message-body. The headers are the same as would be returned in response to a GET.</para>
/// <para>See page 54 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbHEAD = 5,
/// <summary>
/// <para>The POST method is used to post a new entity as an addition to a URI. The URI identifies an entity that consumes the posted data in some fashion.</para>
/// <para>See page 54 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbPOST = 6,
/// <summary>
/// <para>The PUT method is used to replace an entity identified by a URI.</para>
/// <para>See page 55 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbPUT = 7,
/// <summary>
/// <para>The DELETE method requests that a specified URI be deleted.</para>
/// <para>See page 56 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbDELETE = 8,
/// <summary>
/// <para>The TRACE method invokes a remote, application-layer loop-back of the request message. It allows the client to see what is being received at the other end of the request chain for diagnostic purposes. See page 56 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbTRACE = 9,
/// <summary>
/// <para>The CONNECT method can be used with a proxy that can dynamically switch to tunneling, as in the case of SSL tunneling. See page 57 of <a href="https://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbCONNECT = 10,
/// <summary>The TRACK method is used by Microsoft Cluster Server to implement a non-logged trace.</summary>
HttpVerbTRACK = 11,
/// <summary>
/// <para>The MOVE method requests a WebDAV operation equivalent to a copy (COPY), followed by consistency maintenance processing, followed by a delete of the source, where all three actions are performed atomically. When applied to a collection, "Depth" is assumed to be or must be specified as "infinity". See page 42 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbMOVE = 12,
/// <summary>
/// <para>The COPY method requests a WebDAV operation that creates a duplicate of the source resource, identified by the Request URI, in the destination resource, identified by a URI specified in the Destination header. See page 37 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbCOPY = 13,
/// <summary>
/// <para>The PROPFIND method requests a WebDAV operation that retrieves properties defined on the resource identified by the Request-URI. See page 24 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbPROPFIND = 14,
/// <summary>
/// <para>The PROPPATCH method requests a WebDAV operation that sets and/or removes properties defined on the resource identified by the Request-URI. See page 31 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbPROPPATCH = 15,
/// <summary>
/// <para>The MKCOL method requests a WebDAV operation that creates a new collection resource at the location specified by the Request-URI. See page 33 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbMKCOL = 16,
/// <summary>
/// <para>The LOCK method requests a WebDAV operation that creates a lock as specified by the lockinfo XML element on the Request-URI. See page 45 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbLOCK = 17,
/// <summary>
/// <para>The UNLOCK method requests a WebDAV operation that removes a lock, identified by a lock token in the Lock-Token request header, from the resource identified by the Request-URI, and from all other resources included in the lock. See page 51 of <a href="https://www.ietf.org/rfc/rfc2518.txt">RFC 2518</a>.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbUNLOCK = 18,
/// <summary>
/// <para>The SEARCH method requests a WebDAV operation used by Microsoft Exchange to search folders. See the Internet Engineering Task Force (IETF) Internet Draft WebDAV SEARCH for more information, and the <a href="http://www.webdav.org/">WebDAV Web site</a> for possible updates.</para>
/// <para><see href="https://learn.microsoft.com/windows/win32/api/http/ne-http-http_verb#members">Read more on docs.microsoft.com</see>.</para>
/// </summary>
HttpVerbSEARCH = 19,
/// <summary>Terminates the enumeration; is not used to define a verb.</summary>
HttpVerbMaximum = 20,
}
}
}
|