MORE INFORMATION
For the sake of clarity, error handling has been removed from most of the
code in this article. If you use any of this code in your own program,
please implement error handling appropriately. As well, anywhere you find
"...", code has been removed. Please reference the HttpDump and Tear
samples for complete implementations of WinInet coding.
The following code snippet was taken from the HttpDump sample. It
illustrates how to capture a proxy authorization request
(HTTP_STATUS_PROXY_AUTH_REQ):
HttpSendRequest (hReq, NULL, 0, NULL, 0);
HttpQueryInfo (hReq, HTTP_QUERY_STATUS_CODE |
HTTP_QUERY_FLAG_NUMBER, &dwCode, &dwSize, NULL);
if (dwCode == HTTP_STATUS_PROXY_AUTH_REQ)
A check for HTTP_STATUS_PROXY_AUTH_REQ can be added to the Tear MFC sample
to check for HTTP_STATUS_PROXY_AUTH_REQ:
pFile->SendRequest();
pFile->QueryInfoStatusCode(dwRet);
if (dwRet == HTTP_STATUS_PROXY_AUTH_REQ)
Both samples can successfully handle HTTP_STATUS_PROXY_AUTH_REQ by
providing a user interface to collect the username and password for proxy
authorization. The HttpDump sample does so with the following code:
if ( InternetErrorDlg (GetDesktopWindow(),
hReq, ERROR_INTERNET_INCORRECT_PASSWORD,
FLAGS_ERROR_UI_FILTER_FOR_ERRORS |
FLAGS_ERROR_UI_FLAGS_GENERATE_DATA |
FLAGS_ERROR_UI_FLAGS_CHANGE_OPTIONS,
NULL) == ERROR_INTERNET_FORCE_RETRY)
goto again;
WinInet will query hReq to determine the type of error and in the case of
HTTP_STATUS_PROXY_AUTH_REQ, will present the user with the dialog box to
collect the username and password for proxy authorization.
MFC wraps the InternetErrorDlg call and will attempt the proxy
authorization with the following code:
dwPrompt = pFile->ErrorDlg(NULL, ERROR_INTERNET_INCORRECT_PASSWORD,
FLAGS_ERROR_UI_FLAGS_GENERATE_DATA |
FLAGS_ERROR_UI_FLAGS_CHANGE_OPTIONS, NULL);
Unfortunately, CHttpFile::ErrorDlg is broken in the MFC that ships with
Visual C++ versions prior to 6.0. For additional information on how to call
InternetErrorDlg from an MFC application, please see the following article
in the Microsoft Knowledge Base:
189094 Calling CHttpFile::ErrorDlg Function Causes Errors 127 & 2
The drawback of the using InternetErrorDlg is that the function call
displays a user interface. In some cases, this is not desirable.
There are several ways to handle HTTP_STATUS_PROXY_AUTH_REQ without
displaying a user interface. By far the easiest way to do this is by using
the InternetSetOption function with the flags
INTERNET_OPTION_PROXY_PASSWORD and INTERNET_OPTION_PROXY_USERNAME. This
option can be used only on clients that have Internet Explorer 4.0 or later
loaded as the WinInet that shipped before Internet Explorer 4.0 did not
implement this functionality. It will also be necessary to link with the
updated WinInet.h and WinInet.lib from the Internet Client SDK or Microsoft
Platform SDK. The following code illustrates how to implement this
functionality with straight WinInet:
if (dwCode == HTTP_STATUS_PROXY_AUTH_REQ)
{
// read the data off the request handle and setup buffer see
// handler HttpDump handler for HTTP_STATUS_DENIED for details
...
InternetSetOption (hConnect, INTERNET_OPTION_PROXY_USERNAME,
(LPVOID) szUser, lstrlen (szUser);
InternetSetOption (hConnect, INTERNET_OPTION_PROXY_PASSWORD,
(LPVOID) szPass, lstrlen (szPass);
// calls HttpSendRequest again - see HttpDump
goto again;
The same functionality can be accomplished in an MFC application by
detecting HTTP_STATUS_PROXY_AUTH_REQ, calling CHttpConnection::SetOption, then re-calling CHttpFile::SendRequest.
If the client computer does not have Internet Explorer 4 installed, a good
deal more work will be necessary to avoid using InternetErrorDlg. In this
case, it will be necessary to Base64 encrypt the proxy username and
password and add the Proxy-Authorization header as follows. In this
example, "wWdkd2284lwwdj" is a Base64 encrypted user username:password
combination.
char* rangeHeader = "Proxy-Authorization: Basic wWdkd2284lssdj\r\n";
DWORD dwBuffSize = strlen(rangeHeader);
if (dwCode == HTTP_STATUS_PROXY_AUTH_REQ)
{
HttpAddRequestHeaders(hReq, rangeHeader, dwBuffSize,
HTTP_ADDREQ_FLAG_ADD );
// calls HttpSendRequest again - see HttpDump
goto again;
A sample is available that implements a Base54 encryption algorithm. For
additional information, see the following article in the Microsoft
Knowledge Base:
191239 SAMPLE: Sample Base 64 Encoding and Decoding
The format of the username and password that needs to be encrypted is
"username:password" including the colon. Please reference RFC2068 -
"Hypertext Transfer Protocol -- HTTP/1.1" for further details on this.
MFC WinInet applications can implement the same functionality. To do so,
the application should call CHttpFile::AddRequestHeaders and add the Proxy-
Authorization header as above. The application should then resubmit the
request with CHttpFile::SendRequest.