Difference between revisions of "Xebra Module Content Types"

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:'''
 +
 
 
ARGUMENT = "#A#" FILENAME;
 
ARGUMENT = "#A#" FILENAME;
  
XebraHandler
+
'''XebraHandler:'''
 +
 
 
ARGUMENT = "#A#" "#IIS#" FILENAME;
 
ARGUMENT = "#A#" "#IIS#" FILENAME;
  

Revision as of 09:11, 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:

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#" FILENAME;

XebraHandler:

ARGUMENT = "#A#" "#IIS#" FILENAME;

POST, otherwise

Is any other content-type specified, the text will unedited be added to the argument section:

ARGUMENT = "#A#" TEXT;