RAWINPUTONLY (JANUS DEFINE parameter): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(Automatically generated page update) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle" | <span class="pageSubtitle"></span> | ||
<var>RAWINPUTONLY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | <var>RAWINPUTONLY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
| Line 17: | Line 17: | ||
</ul> | </ul> | ||
This parameter is only available in Version 6.8 and later of | This parameter is only available in Version 6.8 and later of <var class="product">Sirius Mods</var>. | ||
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
Latest revision as of 22:23, 16 April 2013
RAWINPUTONLY is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
RAWINPUTONLY indicates that, regardless of the POST data content-type set by the client, Janus Web Server should do both of the following:
- Save the raw input stream of an HTTP POST.
- Refrain from parsing the input content into form fields.
RAWINPUTONLY is very similar to the RAWINPUT port definition parameter, except that:
- RAWINPUTONLY can be an ON rule parameter, so it can be set for specific URLs.
- RAWINPUT does not prevent Janus Web Server from trying to parse the form parameters, if the
content-typefor the POST is set toapplication/x-www-form-urlencodedormultipart/form-data. RAWINPUTONLY prevents this parsing, so it protects Janus Web Server applications from errors in this parsing. These errors include invalid-form-data errors and request-buffer-full errors.
This parameter is only available in Version 6.8 and later of Sirius Mods.
Valid only for WEBSERV ports.