To properly simulate a Form submission using WinInet, you need to send a
header that indicates the proper Content-Type. For Forms, the proper
Content-Type header is:
In many cases, the server does not respond appropriately if a Content-Type
is not specified. For example, the Active Server Pages component of IIS 3.0
actually checks this header specifically for 'application/x-www-form-
urlencoded' before adding form variables to the "Request.Form" object.
This MIME/Content-Type indicates that the data of the request is a list of
URL- encoded form variables. URL-encoding means that space character (ASCII
32) is encoded as '+', special character such '!' encoded in hexadecimal
form as '%21'.
Here is a snippet of code that uses the MFC WinInet classes to simulate a
Form POST request:
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.