diff --git a/docs/manual/mod/mod_request.html b/docs/manual/mod/mod_request.html new file mode 100644 index 0000000000..5bd37bf6ba --- /dev/null +++ b/docs/manual/mod/mod_request.html @@ -0,0 +1,3 @@ +URI: mod_request.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_request.html.en b/docs/manual/mod/mod_request.html.en new file mode 100644 index 0000000000..f28236f0e0 --- /dev/null +++ b/docs/manual/mod/mod_request.html.en @@ -0,0 +1,97 @@ + + + +request_body - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.3

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.3 > Modules
+
+

Apache Core Features

+
+

Available Languages:

+
+ +
Description:Filters to handle and make available HTTP request bodies
Status:Core
+
+

Directives

+ +
+ +
top
+

KeptBodySize Directive

+ + + + + + + +
Description:Keep the request body instead of discarding it up to +the specified maximum size, for potential use by filters such as +mod_include.
Syntax:KeptBodySize maximum size in bytes
Default:KeptBodySize 0
Context:directory
Status:Core
Module:request_body
+

Under normal circumstances, request handlers such as the + default handler for static files will discard the request body + when it is not needed by the request handler. As a result, + filters such as mod_include are limited to making GET requests + only when including other URLs as subrequests, even if the + original request was a POST request, as the discarded + request body is no longer available once filter processing is + taking place.

+ +

When this directive has a value greater than zero, request + handlers that would otherwise discard request bodies will + instead set the request body aside for use by filters up to + the maximum size specified. In the case of the mod_include + filter, an attempt to POST a request to the static + shtml file will cause any subrequests to be POST + requests, instead of GET requests as before.

+ +

This feature makes it possible to break up complex web pages and + web applications into small individual components, and combine + the components and the surrounding web page structure together + using mod_include. The components can take the + form of CGI programs, scripted languages, or URLs reverse proxied + into the URL space from another server using + mod_proxy.

+ +

Note: Each request set aside has to be set + aside in temporary RAM until the request is complete. As a result, + care should be taken to ensure sufficient RAM is available on the + server to support the intended load. Use of this directive + should be limited to where needed on targeted parts of your + URL space, and with the lowest possible value that is still big + enough to hold a request body.

+ +

If the request size sent by the client exceeds the maximum + size allocated by this directive, the server will return + 413 Request Entity Too Large.

+ + +

See also

+ +
+
+
+

Available Languages:

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_request.xml.meta b/docs/manual/mod/mod_request.xml.meta new file mode 100644 index 0000000000..405ca67c78 --- /dev/null +++ b/docs/manual/mod/mod_request.xml.meta @@ -0,0 +1,11 @@ + + + + mod_request + /mod/ + .. + + + en + + diff --git a/docs/manual/rewrite/rewrite_guide.html.en b/docs/manual/rewrite/rewrite_guide.html.en index 7ee43fe531..36f94ec8e9 100644 --- a/docs/manual/rewrite/rewrite_guide.html.en +++ b/docs/manual/rewrite/rewrite_guide.html.en @@ -26,7 +26,7 @@ reference documentation. It describes how one can use Apache's mod_rewrite to solve typical URL-based problems with which webmasters are - commonony confronted. We give detailed descriptions on how to + commonly confronted. We give detailed descriptions on how to solve each problem by configuring URL rewriting rulesets.

ATTENTION: Depending on your server configuration