Table of Contents
Advertisement
Syntax
chunked-uploads {on | off}
Parameters
on
off
Guidelines
The gateway might send an HTTP 1.1 request to the backend server. In this case,
the body of the document can be delimited by either Content-Length or chunked
encoding. All servers will understand how to interpret Content-Length, and many
applications will fail to understand chunked, so Content-Length is generally used.
However doing so interferes with the ability of the appliance to fully stream. If
you must stream full documents towards the backend, this property should be
turned on. Unlike all other HTTP 1.1 features that can be negotiated down at
runtime, if necessary, you must know beforehand that the server you are
communicating with is RFC 2616 compatible. You might also consider leaving this
property turned off and turning it on a per-URL basis with the User Agent
configuration.
Examples
v Enables HTTP 1.1 chunked encoding and subsequently disable chunked
compression
Controls GZIP compression negotiation between the Multi-Protocol Gateway and
the backend server.
Syntax
compression {on | off}
Parameters
on
off
Examples
v Enables compression negotiation and subsequently disables such negotiation
Enables chunked encoding when sending HTTP 1.1 requests to the
backend server.
(default) Disables chunked encoding when sending HTTP 1.1 requests to
the backend server.
encoding support, thus restoring the default state.
# chunked-uploads on
. .
.
# chunked-uploads off
#
Enables GZIP compression negotiation on backend.
Disables GZIP compression negotiation on backend.
thus restoring the default state.
# compression on
. .
.
# compression off
#
Chapter 49. Multi-Protocol Gateway configuration mode
439
Advertisement
Table of Contents
