What does HRESULT 0x80072EF4 (WININET_E_NOT_PROXY_REQUEST) mean?

 
Previous Next
WININET_E_INCORRECT_HANDLE_STATE WININET_E_REGISTRY_VALUE_NOT_FOUND

WININET_E_NOT_PROXY_REQUEST

WININET_E_NOT_PROXY_REQUEST is a WinINet HRESULT. It means that a request or configuration operation requiring a direct WinINet session was attempted through a session configured for proxy access.

What to check for WININET_E_NOT_PROXY_REQUEST

  • Inspect the access type and proxy settings used when the parent Internet handle was created.
  • Use a handle configured for the required direct or proxy operation instead of changing behavior mid-request.
  • Check organization proxy policy before bypassing a proxy to work around the error.

Microsoft: WinINet overview

Diagnostic interpretation of WININET_E_NOT_PROXY_REQUEST

WININET_E_NOT_PROXY_REQUEST has the HRESULT value 0x80072EF4. AllStat records the condition as “The request cannot be made on a Proxy session”. For WININET_E_NOT_PROXY_REQUEST, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.

Evidence to capture for WININET_E_NOT_PROXY_REQUEST

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80072EF4 value before a wrapper converts it to an exception or Boolean result.
  • Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions WININET_E_NOT_PROXY_REQUEST or the wininet / proxy / request operation.
  • Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original wininet / proxy / request condition.

Retry and recovery for WININET_E_NOT_PROXY_REQUEST

Retry WININET_E_NOT_PROXY_REQUEST only when the owning API documents a transient state or after the condition described as “The request cannot be made on a Proxy session” has changed. For WININET_E_NOT_PROXY_REQUEST, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.

Looking for a different code? Search another status or error code.