HTTP multipart/form-data method (aka RFC 1867)
An experimental protocol proposed for the Internet community. It is a suggested extension to HTML that would allow content providers to express file upload requests uniformly, and a MIME-compatible representation for file upload responses.
Mapping module
A self-registering server that creates the appropriate entry in the Posting Acceptor’s mapping modules registry key during registration.
PostInfo file
The PostInfo file is used by Web Post API and the ActiveX Upload control to automatically set up a client to publish content to your server. A sample PostInfo file (postinfo.asp) is provided in Posting Acceptor.
The following table provides additional details for the parameters in the sample PostInfo file.
|
Value |
Description |
|
Version |
Must be 1.5 to indicate compatibility with this release. |
|
Provider’s GUID |
Globally unique identifier. |
|
PostingURL |
URL to post to. |
|
TargetURL |
Target URL for the uploaded content. |
|
Default page |
Name of default page used on the server. For example, the IIS default is "default.htm." |
PostingURL
PostingURL is used by content providers to post files. It is the full URL path to the Posting Acceptor, and appears as the following default unless otherwise specified:
http:\\your_server_name\path-to-PostingAcceptor\?PUBLISH
Post-ProcessingURL
Post-processingURL is part of the PostingURL. It can be created by appending the PostingURL to read:
http:\\your_server_name\path-to-PostingAcceptor\?PUBLISH?http:\\Post-processingURL
TargetURL
The TargetURL is the final target for a content provider’s uploaded files, as well as the URL they use to retrieve content.
WebPost API-client side
The client side of the WebPost API contains the flupl.cab, Web Publishing Wizard, and any other application that uses ActiveX controls.