When using the XHTTPF_REQUPLOAD flag to upload files, the generated request will contain a header for each file, specifying a content-type and name attribute. For example, if request = "myfile.qry", the generated header will look something like:

Content-Disposition: form-data; name="file"; filename="myfile.qry"

Content-Type: application/octet-stream

The filename attribute (set to "myfile.qry" here) may not be changed, but shouldn't be a problem as it matches the normal format used by the standard HTML form type for file uploads. The name attribute ("file" in this default case) is arbitrary; in most cases the server will ignore it, but in some cases (when more than one file or file type is being uploaded) it may be used to communicate to the server the nature or meaning of the file. The Content-Type header is automatically determined based on some simple heuristics involving the file extension. In cases where the default name and Content-Type values are not acceptable to the server, as of ashnet.dll 1.4(129) you can specify them by inserting, in front of each filename, a prefix of the form "Content-Type=<type>|<name>=" where <type> is the desired content-type, and <name> is the desired value of the 'name' attribute. For example, if:

request = "Content-Type: text/html|queryfile=myfile.qry"

the generated header would look like:

Content-Disposition: form-data; name="queryfile"; filename="myfile.qry"

Content-Type: text/html