Skip to content

ihttpcontext-getexecuteflags-method.md

Latest commit

 

History

History
71 lines (51 loc) · 4.49 KB

ihttpcontext-getexecuteflags-method.md

File metadata and controls

71 lines (51 loc) · 4.49 KB
title IHttpContext::GetExecuteFlags Method
description Learn how the IHttpContext::GetExecuteFlags method retrieves the execution flags for the current context.
ms.date 10/07/2016
ms.assetid d4470530-25e6-17cb-d5fb-d817bb02e98c

IHttpContext::GetExecuteFlags Method

Retrieves the execution flags for the current context.

Syntax

virtual DWORD GetExecuteFlags(  
   VOID  
) const = 0;

Parameters

This method takes no parameters.

Return Value

A DWORD that contains the execution flags.

Remarks

The GetExecuteFlags method retrieves the execution flags for the current context. The following table lists the possible values for these flags.

Value Description
EXECUTE_FLAG_NO_HEADERS Suppress the HTTP headers for the child request.
EXECUTE_FLAG_IGNORE_CURRENT_INTERCEPTOR Ignore the current script map handler for this request chain.
EXECUTE_FLAG_IGNORE_APPPOOL Execute the request even if the child request is not in the same application pool.
EXECUTE_FLAG_DISABLE_CUSTOM_ERROR Disable custom errors for the child request.
EXECUTE_FLAG_SAME_URL The URL for the child request is the same as the parent request.
EXECUTE_FLAG_BUFFER_RESPONSE Do not flush the child response; return the response to the parent request.
EXECUTE_FLAG_HTTP_CACHE_ELIGIBLE The child response is still eligible for caching by Http.sys.

Example

The following code example demonstrates how to create an HTTP module that performs the following tasks:

  1. The module registers for the RQ_SEND_RESPONSE notification.

  2. The module creates a CHttpModule class that contains an OnSendResponse method.

  3. When a Web client requests a URL, IIS calls the module's OnSendResponse method. This method performs the following tasks:

    1. Clears the existing response buffer and sets the MIME type for the response.

    2. Retrieves the execution flags for the current context by using the GetExecuteFlags method.

    3. Tests for individual execution flags and returns the status to the Web client.

  4. The module removes the CHttpModule class from memory and then exits.

[!code-cppIHttpContextGetExecuteFlags#1]

Your module must export the RegisterModule function. You can export this function by creating a module definition (.def) file for your project, or you can compile the module by using the /EXPORT:RegisterModule switch. For more information, see Walkthrough: Creating a Request-Level HTTP Module By Using Native Code.

You can optionally compile the code by using the __stdcall (/Gz) calling convention instead of explicitly declaring the calling convention for each function.

Requirements

Type Description
Client - IIS 7.0 on [!INCLUDEwinvista]
- IIS 7.5 on Windows 7
- IIS 8.0 on Windows 8
- IIS 10.0 on Windows 10
Server - IIS 7.0 on [!INCLUDEwinsrv2008]
- IIS 7.5 on Windows Server 2008 R2
- IIS 8.0 on Windows Server 2012
- IIS 8.5 on Windows Server 2012 R2
- IIS 10.0 on Windows Server 2016
Product - IIS 7.0, IIS 7.5, IIS 8.0, IIS 8.5, IIS 10.0
- [!INCLUDEiisexp75], [!INCLUDEiisexp80], [!INCLUDEiisexp100]
Header Httpserv.h

See Also

IHttpContext Interface
IHttpContext::ExecuteRequest Method