This module is contained in the mod_babble.c file, and
is not compiled into the server by default. It provides a means
of generating responses of any desired size, primarily for testing
purposes. The response constists of specific pattern replicated
sufficient times to make up the specified number of bytes, with the
last byte being a newline. The response content-type is
text/plain, and the Content-length
response header field is set to make the response cacheable.
The mod_babble directives allow you to specify the
default size and pattern of the babble response, but individual
responses can be tailored using arguments specified in the URL
itself. Two keywords are recognised:
size=numbytesBabbleMaxSize directive),
the maximum number of bytes will be sent instead. If numbytes
is negative and a
BabbleStreaming On
directive is in effect, the module will omit the
Content-length response header field and emit up to
4GB of content.pattern=stringBabblePatternLock directive
in the URI scope, the specified string will be the response's
replication pattern instead of the default set by the
BabbleDefaultPattern directive.
Keywords may be combined in the URL, separated by any legal
non-alphanumeric character, with the first occurrences
of any duplicate keywords taking precedence. E.g.,
"?size=100;pattern=foo;size=200" will result in a
response size of 100 bytes.
BabbleDefaultPattern
directive
Syntax: BabbleDefaultPattern "string"
Default: BabbleDefaultPattern "deadbeef"
Context: server config, virtual host, directory, .htaccess
Override: Options
Status: Third-party
Module: mod_babble
This directive allows you to specify the default replication pattern used to compose the response body.
Example:
BabbleDefaultPattern "Boo!"
See the section on specifying parameters in the URL for details of how this default may be overridden.
BabbleDefaultSize
directive
Syntax: BabbleDefaultSize "numbytes"
Default: BabbleDefaultSize 8192
Context: server config, virtual host, directory, .htaccess
Override: Options
Status: Third-party
Module: mod_babble
The BabbleDefaultSize directive sets the default
size of any response in the absence of a size
keyword setting in the request URL. The response size is always
less than or equal to the maximum size (set by
BabbleMaxSize),
regardless of the
setting of this directive or a URL keyword.
Example:
BabbleDefaultSize 4096
See the section on specifying parameters in the URL for details of how this default may be overridden.
BabbleMaxSize directive
Syntax: BabbleMaxSize "numbytes"
Default: BabbleMaxSize 8192
Context: server config, virtual host, directory
Override: Not allowed in .htaccess files
Status: Third-party
Module: mod_babble
This directive sets the absolute maximum size of of any babble response within its scope.
Example:
BabbleMaxSize 102400
This directive can only appear in the server-wide configuration files, and exists primarily to impose a limit on resource consumption by the module.
BabblePatternLock
directive
Syntax: BabblePatternLock On | Off
Default: BabblePatternLock Off
Context: server config, virtual host, directory, .htaccess
Override: Options
Status: Third-party
Module: mod_babble
This directive prevents the use of the pattern URL
keyword within its scope. Any occurrence of the keyword on
URLs to which this directive applies with an On
setting will be ignored.
Example:
BabblePatternLock On
This directive is intended to restrict the use of patterns that may cause problems for browsers or clients when replicated in the response body.
BabbleStreaming
directive
Syntax: BabbleStreaming On | Off
Default: BabbleStreaming Off
Context: server config, virtual host, directory
Override: Not allowed in .htaccess files
Status: Third-party
Module: mod_babble
This directive controls whether the module can be put into 'streaming'
mode. If enabled, and a request is made with a negative size
URL keyword, the module will omit the Content-length
response header field and emit up to 4GB of content. Typically the
server timeout will trigger before the total content is delivered.
Example:
BabbleStreaming On
This directive is intended to allow stress testing when desired,
while ordinarily limiting the network and CPU performance impact.
It is a server-wide setting and cannot be overridden in
.htaccess files.