Contents Index Topic Contents | ||
Previous Topic: IHttpNegotiate::BeginningTransaction Next Topic: IHttpSecurity::OnSecurityProblem |
IHttpNegotiate::OnResponse
HRESULT OnResponse( [in] DWORD dwResponseCode, [in] LPCWSTR szResponseHeaders, [in] LPCWSTR szRequestHeaders, [out] LPWSTR * pszAdditionalRequestHeaders );Allows the client of a bind operation to examine the response headers, optionally terminate the bind operation, and add HTTP headers to a request before resending the request.
- Returns one of the following values:
S_OK The operation completed successfully. If dwResponseCode indicates an error, any szAdditionalRequestHeaders are appended and the request is sent again. E_ABORT Terminate the HTTP transaction. E_INVALIDARG The parameter is invalid.
- dwResponseCode
- HTTP response code returned in response to a previous HTTP request. For information about these codes, see the HTTP specification.
- szResponseHeaders
- Response headers from the HTTP server. For more information, see the HTTP specification.
- szRequestHeaders
- If dwResponseCode indicates an error, contains HTTP request headers that will be used when the request is sent again.
- pszAdditionalRequestHeaders
- If dwResponseCode indicates an error, contains optional, additional headers to add before the request is sent again. If the specified header value conflicts with existing values in szRequestHeaders, the new headers take precedence. If pszAdditionalRequestHeaders is set to NULL, no headers are added to the HTTP request.
The URL moniker calls this method when it receives a response to an HTTP request. If dwResponseCode indicates a success, the client can examine the response headers and can optionally abort the bind operation. If dwResponseCode indicates a failure, the client can add HTTP headers to the request before it is sent again.
Note that if multiple clients have registered on the bind context for a given bind operation, more than one of these clients can provide an IHttpNegotiate callback interface. Every client providing this callback receives notifications. Each one is given a chance to add HTTP headers or to abort the HTTP transaction. In such cases, the last client to receive callback notification is the client driving the download operation, and it will dictate the final decision.
See also IHttpNegotiate::BeginningTransaction
Top of Page
© 1997 Microsoft Corporation. All rights reserved. Terms of Use.