Difference between revisions of "Xebra Module Content Types"
(→POST, multipart/form-data) |
|||
(One intermediate revision by the same user not shown) | |||
Line 20: | Line 20: | ||
The submitted file is saved to a temporary file on the disk and its path is appended in the arguments section. Only upload of one file at a time is supported currently. Since XebraHandler stores the uploaded file differently, it adds a IIS_FLAG (#IIS#) to the message. | The submitted file is saved to a temporary file on the disk and its path is appended in the arguments section. Only upload of one file at a time is supported currently. Since XebraHandler stores the uploaded file differently, it adds a IIS_FLAG (#IIS#) to the message. | ||
− | mod_xebra: | + | '''mod_xebra:''' |
− | + | ||
− | XebraHandler | + | ARGUMENT = "#A#" "#FUPA# FILENAME; |
− | ARGUMENT = "#A#" "# | + | |
+ | '''XebraHandler:''' | ||
+ | |||
+ | ARGUMENT = "#A#" "#FUPI#" FILENAME; | ||
==POST, otherwise== | ==POST, otherwise== |
Latest revision as of 13:44, 12 August 2009
About | Installation | Documentation | Tutorials | Frequently Asked Questions
Mod_xebra and XebraHandler create the request message that is sent to the xebra server according to the requests Content-Type in the following way:
Contents
GET
In the arguments section key value pairs are appended:
ARGUMENT = "#A#" {"#$#" KEY "=" VALUE};
POST, application/x-www-form-urlencoded
In the arguments section key value pairs are appended:
ARGUMENT = "#A#" {"#$#" KEY "=" VALUE};
POST, multipart/form-data
The submitted file is saved to a temporary file on the disk and its path is appended in the arguments section. Only upload of one file at a time is supported currently. Since XebraHandler stores the uploaded file differently, it adds a IIS_FLAG (#IIS#) to the message.
mod_xebra:
ARGUMENT = "#A#" "#FUPA# FILENAME;
XebraHandler:
ARGUMENT = "#A#" "#FUPI#" FILENAME;
POST, otherwise
Is any other content-type specified, the text will unedited be added to the argument section:
ARGUMENT = "#A#" TEXT;