Thread: Winhttpopenrequest encoding issue

I noticed that '_' (underscore) characters are being converted to ' ' (whitespace) in my URL. I'm not sure what I should do to get around this issue. Also, if someone knows of any MS APIs that do modified base64 encoding, I'd be very grateful if they told me.

Thanks so much in advance.

Thanks for the suggestion Salem.
hRequest = WinHttpOpenRequest( hConnect,
A2W(httpMethod),
A2W(relativeURI),
L"HTTP/1.1",
WINHTTP_NO_REFERER,
WINHTTP_DEFAULT_ACCEPT_TYPES,
WINHTTP_FLAG_SECURE);

is what my call looks like, where relativeURI is something like
bbb83Dk-UT5tOZibYBJZc3tOak0-prigwn_3pCh1YTw1
The underscore is converted to a space.

Also if I wanted to convert
bbb83Dk+UT5tOZibYBJZc3tOak0+prigwn/3pCh1YTw1=
to the above modified base64 encoded format, I don't know what MS API to use for a native C++ app. I cannot use any managed code and I care about multi byte chars. I'm loath to write one unless I'm sure there's no other way out.

Code:

#include <windows.h>
#include <winhttp.h>
#pragma comment(lib, "winhttp.lib")
int main()
{
    HINTERNET hSession = WinHttpOpen(L"Test", WINHTTP_ACCESS_TYPE_NO_PROXY, NULL, NULL, 0);
    if(hSession)
    {
        HINTERNET hCon = WinHttpConnect(hSession, L"www.google.com", INTERNET_DEFAULT_HTTP_PORT, 0);
        if(hCon)
        {
            HINTERNET hRequest = WinHttpOpenRequest(
                hCon,
                L"GET",
                L"bbb83Dk-UT5tOZibYBJZc3tOak0-prigwn_3pCh1YTw1",
                L"HTTP/1.1",
                WINHTTP_NO_REFERER,
                WINHTTP_DEFAULT_ACCEPT_TYPES,
                0
            );
            if(hRequest)
            {
                WinHttpSendRequest(hRequest, NULL, 0, NULL, 0, 0, 0);
                WinHttpCloseHandle(hRequest);
            }
            WinHttpCloseHandle(hCon);
        }
        WinHttpCloseHandle(hSession);
    }
    return 0;
}

Originally Posted by wireshark

GET /bbb83Dk-UT5tOZibYBJZc3tOak0-prigwn_3pCh1YTw1 HTTP/1.1
Connection: Keep-Alive
User-Agent: Test
Host: www.google.com

Whatever your problem is, it's not an intrinsic behaviour of the function.

Gaaa. Never trust another's logging capabilities. I don't know why I didn't try this myself. Any API that does modified base64 encoding though?