Local Traffic Manager system that includes the Link Controller offers several features that you can use to intelligently control your HTTP, HTTPS, and FTP traffic. Examples of these features are the insertion of headers into HTTP requests and the compression of HTTP server responses.
These features are available through configuration of HTTP or FTP profiles.
is a group of settings, with values, that corresponds to a specific type of traffic, such as HTTP traffic. A profile defines the way that you want the BIG-IP system to manage that traffic type.
In addition to HTTP and FTP profiles, the BIG-IP system includes other
features to help you manage your application traffic, such as health monitors for checking the health of HTTP and FTP services, and iRulesTM
for querying or manipulating HTTP header or content data.
summarizes the capabilities within the BIG-IP system for managing HTTP and FTP traffic and shows the BIG-IP object that you configure to implement each feature.
You can configure HTTP profiles to ensure that HTTP traffic management
suits your specific needs. These configuration settings are organized into several categories on the New HTTP Profile screen in the Configuration utility: General Properties, Settings, Compression, and RAM Cache. You can configure these settings when you create a profile, or after profile creation by modifying the profiles settings. For specific procedures on configuring a profile, see Chapter 13, Understanding Profiles
For the profile settings that appear in the General Properties and Settings
areas of the HTTP Profile screen, you can specify values where none exist, or modify any default values to suit your needs. For information about other HTTP profile settings, see Configuring FTP profile settings
You can use the default http
profile as is, or create a custom HTTP profile. The http
profile is considered a default profile because it does not inherit setting values from a parent profile.
shows the profile settings for an HTTP type of profile. For those settings that have default values, you can retain those default settings or modify them. Following this table are descriptions of the settings and the procedure for changing them.
To create an HTTP profile, you must specify a unique name for the profile.
setting is one of only two settings for which you must actively specify a value when creating an HTTP profile; all other settings have default values.
To specify a profile name, simply locate the Name
setting and type a unique name for the profile.
Every profile that you create is derived from a parent profile. You can use
the default http
profile as the parent profile, or you can use another HTTP profile that you have already created.
To specify a parent profile, locate the Parent Profile
setting and select a profile name.
Sometimes, you might want to inspect and/or modify HTTP application
data, such as compressing the content of an HTTP response. Such inspections or modifications require that the response be unchunked
, that is, not in chunked encoding. Using the Response Chunking
settings, the BIG-IP system can unchunk a chunked response before performing an action on that response.
Possible values for this setting are Unchunk
, and Preserve
. The default value is Selective
describes each of these values and the action that the BIG-IP system takes, depending on whether an original response is chunked or unchunked.
| || || |
| || |The BIG-IP system unchunks the response and
processes the HTTP content, and passes the response on as unchunked. The connection closes when all data is sent to the client as indicated by the Connection: Close
| || |The BIG-IP system unchunks the response,
processes the HTTP content, re-adds the chunk trailer headers, and then passes the response on as chunked. Any chunk extensions are lost.
| || || |
| || |The BIG-IP system leaves the response
chunked, processes the HTTP content, and passes the response on untouched. Note that if HTTP compression is enabled, the BIG-IP system does not compress the response.
| |With the Maximum Header Size
setting, you can specify the maximum size that the BIG-IP system allows for HTTP headers. The default value is 32768
and is represented in bytes.
Normally, a client cannot make a request until the previous request has
received a response. HTTP/1.1 pipelining allows clients to make requests even when prior requests have not received a response. For this to succeed, however, destination servers must include support for pipelining. This feature enables that support on the BIG-IP system.
To enable pipelining, locate the Pipelining
setting and check the box. By default, this feature is set to Enabled
When using connection pooling, which allows clients to make use of
existing server-side connections, you can insert the XForwarded For
header into a request. When you configure the BIG-IP system to insert this header, the target server can identify the request as coming from a client other than the client that initiated the connection. The default setting is Disabled
The LWS Maximum Columns
setting specifies the maximum number of columns allowed for a header that is inserted into an HTTP request.
To configure the LWS Maximum Columns setting, specify a maximum value. The default value for this setting is 80. The LWS Separator
setting specifies the separator that the BIG-IP system should use between HTTP headers when a header exceeds the maximum width specified by the LWS Maximum Columns
To configure the LWS Separator
setting, specify a value for the separator. This setting has no default value.
The Maximum Requests
setting specifies the maximum number of requests that the system allows for a single Keep-Alive connection. When the specified limit is reached, the final response contains a Connection: close
header is followed by the closing of the connection. The default setting is 0
, which in this case means that the system allows an infinite number of requests per Keep-Alive
You can tailor FTP profile settings to your specific needs. For those settings
that have default values, you can retain those default settings or modify them. You can modify any settings either when you create the profile, or at any time after you have created it. For specific procedures on configuring a profile, see Chapter 13, Understanding Profiles
lists these configurable settings, along with a short description of each and the default values. Following this table are descriptions of specific settings.
To create an FTP profile, you must specify a unique name for the profile.
setting is one of only two settings for which you must actively specify a value when creating an FTP profile; all other settings have default values.
Every profile that you create is derived from a parent profile. In the Parent Profile
setting, you can select the default ftp
profile as the parent profile, or you can select another FTP profile that you have already created.
Because IP version 6 addresses are not limited to 32 bits (unlike IP version 4
addresses), compatibility issues can arise when using FTP in mixed IP-version configurations.
Enabled by default, the Translate Extended
setting causes the BIG-IP system to automatically translate FTP commands when a client-server configuration contains both IP version 4 and IP version 6 systems. For example, if a client system running IP version 4 sends the FTP PASV
command to a server running IP version 6, the BIG-IP system automatically translates the PASV
command to the equivalent FTP command for IP version 6 systems, EPSV
It is highly unlikely that you need to change the default value (Enabled
) for this setting. The only case where you might want to disable this setting is when sending an EPSV
command to an IP version 4 system, such as when testing an FTP server.
The Data Port
setting allows the FTP service to run on an alternate port. You can use the default port number 20
, or specify another port number.