AskF5 | Release Note: BIG-IP WebAccelerator version 11.1.0

AskF5 Knowledge Base

Applies To:

Show Versions

Release Note: BIG-IP WebAccelerator version 11.1.0

Original Publication Date: 03/22/2012

Summary:

This release note documents the version 11.1.0 release of BIG-IP WebAccelerator system.

Contents:

- Supported hardware
- User documentation for this release
- New in 11.1.0
- New in 11.0.0
- Installation overview
     - Installation checklist
     - Installing the software
     - Post-installation tasks
     - Installation tips
- Upgrading from earlier versions
- Fixes in 11.1.0
- Fixes in 11.0.0
- Known issues
- Contacting F5 Networks
- Legal notices

Supported hardware

You can apply the software upgrade to systems running software versions 10.x. For a list of supported platforms, see SOL9412: The BIG-IP release matrix. For information about which platforms support which module combinations, see SOL10288: BIG-IP software and platform support matrix.

User documentation for this release

For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IP WebAccelerator / VE 11.1.0 Documentation page.

New in 11.1.0

WebAccelerator Virtual Edition

This release provides WebAccelerator™ Virtual Edition (VE). WebAccelerator VE, which runs as a virtual machine in specifically supported hypervisor environments, emulates a hardware-based WebAccelerator system running a VE-compatible version of software.

WebAccelerator Predefined Generic Policies

This release includes a new WebAccelerator predefined generic policy, and enhancements to predefined generic policies, as described in the following table.

Version 11.x Predefined Generic Policy	Description
Generic Policy - Complete. New policy.	This predefined acceleration policy is ideal for Apache HTTP servers, Internet Information Services (IIS) web servers, WebLogic application servers, and IBM Websphere Application Servers. HTML pages are cached and Intelligent Browser Referencing is enabled.
Generic Policy - Enhanced. (Formerly called Level 2 Delivery.)	This predefined acceleration policy is ideal for Apache HTTP servers, Internet Information Services (IIS) web servers, WebLogic application servers, and IBM Websphere Application Servers. HTML pages are cached and Intelligent Browser Referencing is enabled for includes.
Generic Policy - Extension Based. (Formerly called Ecommerce.)	This predefined acceleration policy is ideal for High Performance policy for Ecommerce applications that uses File Extensions instead of mime-types. This application policy is ideal if response-based matching is not required.
Generic Policy - Fundamental. (Formerly called Level 1 Delivery.)	This predefined acceleration policy is ideal for Apache HTTP servers, Internet Information Services (IIS) web servers, WebLogic application servers, and IBM Websphere Application Servers. HTML pages are always proxied and Intelligent Browser Referencing is disabled.

Acceleration Policy Editor Role

This release provides a Acceleration Policy Editor role to manage and customize acceleration policies for the BIG-IP^® WebAccelerator™ system. This role provides full access to WebAccelerator system features and functionality, and read-only access to all other BIG-IP features and functionality.

New in 11.0.0

HTTP Compression profile

The HTTP Compression profile reduces the amount of data to be transmitted, thereby significantly reducing bandwidth usage. All of the tasks needed to configure HTTP compression on the BIG-IP system, as well as the compression software itself, are centralized on the BIG-IP system. The tasks needed to configure HTTP compression for objects in a WebAccelerator policy node are available in the WebAccelerator system, but an HTTP compression profile must be enabled for them to function.

Web Acceleration profile

When used with the WebAccelerator system, the Web Acceleration profile includes an ordered list of associated WebAccelerator applications, each of which defines the host names, IP addresses, and policy that is applied to a request that matches the specified host name or IP address.

Request Logging profile

With the Request Logging profile you can specify the data and the format for HTTP requests and responses that you want to include in a log file. If you prefer, you can tailor the information that appears in the logs so that the logs work seamlessly with whatever analysis tools you use for your origin web server's HTTP log files.

Lifetime rules

This release of the WebAccelerator system introduces design simplifications and improvements to Lifetime rules.

Interoperability for Local Traffic Manager, Global Traffic Manager, and WebAccelerator systems

This release provides the ability to provision Local Traffic Manager, Global Traffic Manager, and WebAccelerator systems concurrently.

PDF linearization

Through the Configuration utility, the WebAccelerator system provides the ability to display a requested page more quickly by using PDF linearization (optimization). PDF linearization prepares the PDF file for byte serving, which enables the WebAccelerator system to provide individual pages to a client when it receives byte-range requests.

Metadata cache responses

Because not all web applications generate ETags consistently, the WebAccelerator system creates its own ETag for each cached document that is based on a signature, or checksum, of the document's content. The WebAccelerator system stores content signatures in the Metadata cache for other optimizations, including Intelligent Browser Referencing. WebAccelerator system applications provide options to always or never send metadata.

Via headers

The Via header, configured in an HTTP profile, provides information about each intermediate router that forwards a message. Intermediate routers between a client and an origin web server use the Via header to indicate intermediate protocols and recipients.

Debug options

This setting is used for troubleshooting purposes, enabling the WebAccelerator system to optionally insert an X-WA-Info response header that includes specific codes, which describe the properties and history of the object.

WebAccelerator application performance monitoring

This release provides the ability to enable performance monitoring per WebAccelerator application. The WebAccelerator system's performance reports provide information about page requests, the frequency of those requests, and how well the WebAccelerator system serviced those requests from cache. Additionally, performance reports provide information about the application, policy, policy node, HTTP response status, S-code, size range of the response, response object type, and ID of the WebAccelerator system or browser making the request.

WebAccelerator statistics in Dashboard

The BIG-IP Dashboard provides WebAccelerator statistics with this release, including data specific to memory usage, performance metrics, throughput metrics, and cache metrics.

SNMP access

This release of the WebAccelerator system provides SNMP access. The following table includes all WebAccelerator object identifiers, object types, and a description of each. All object identifiers and object types can be found in the /usr/share/snmp/mibs/F5-BIGIP-WAM-MIB.txt file.

Object Identifier	Object Type	Description
1	wamAppStatName	The name of the WebAccelerator application.
2	wamAppStatVsName	The name of the virtual server.
3	wamAppStatRqstTotal	The total number of requests made to this WebAccelerator application.
4	wamAppStatProxied	The total number of requests proxied by this WebAccelerator application.
5	wamAppStatProxiedBytes	The total number of requests proxied by this WebAccelerator application measured in bytes.
6	wamAppStatProxied1500	The total number of requests between 0 and 1500 bytes proxied by this WebAccelerator application.
7	wamAppStatProxied10k	The total number of requests between 1500 and 10K bytes proxied by this WebAccelerator application.
8	wamAppStatProxied50k	The total number of requests between 10K and 50K bytes proxied by this WebAccelerator application.
9	wamAppStatProxied100k	The total number of requests between 50K and 100K bytes proxied by this WebAccelerator application.
10	wamAppStatProxied500k	The total number of requests between 100K and 500K bytes proxied by this WebAccelerator application.
11	wamAppStatProxied1m	The total number of requests between 500K and 1M bytes proxied by this WebAccelerator application.
12	wamAppStatProxied5m	The total number of requests between 1M and 5M bytes proxied by this WebAccelerator application.
13	wamAppStatProxiedLarge	The total number of requests larger than 5M bytes proxied by this WebAccelerator application.
14	wamAppStatProxiedNew	The total number of new requests proxied by this WebAccelerator application.
15	wamAppStatProxiedExpired	The total number of expired requests proxied by this WebAccelerator application.
16	wamAppStatProxiedPerPolicy	The total number of requests proxied per policy by this WebAccelerator application.
17	wamAppStatProxiedPerIRule	The total number of requests proxied per iRule by this WebAccelerator application.
18	wamAppStatProxiedPerInvalidation	The total number of requests proxied per invalidation rules by this WebAccelerator application.
19	wamAppStatProxiedPerClientRequest	The total number of requests proxied per headers from client request by this WebAccelerator application.
20	wamAppStatProxiedBypass	The total number of proxy requests bypassed by this WebAccelerator application.
21	wamAppStatFromCache	The total number of requests served from cache by this WebAccelerator application.
22	wamAppStatFromCacheBytes	The total number of request bytes served from cache by this WebAccelerator application.
23	wamAppStatFromCache1500	The total number of requests between 0 and 1500 bytes served from cache by this WebAccelerator application.
24	wamAppStatFromCache10k	The total number of requests between 1500 and 10K bytes served from cache by this WebAccelerator application.
25	wamAppStatFromCache50k	The total number of requests between 10K and 50K bytes served from cache by this WebAccelerator application.
26	wamAppStatFromCache100k	The total number of requests between 50K and 100K bytes served from cache by this WebAccelerator application.
27	wamAppStatFromCache500k	The total number of requests between 100K and 500K bytes served from cache by this WebAccelerator application.
28	wamAppStatFromCache1m	The total number of requests between 500K and 1M bytes served from cache by this WebAccelerator application.
29	wamAppStatFromCache5m	The total number of requests between 1M and 5M bytes served from cache by this WebAccelerator application.
30	wamAppStatFromCacheLarge	The total number of requests larger than 5M bytes served from cache by this WebAccelerator application.
31	wamAppStatOws2xx	The number of origin web server responses in the range of 200 to 206 (successful responses).
32	wamAppStatOws3xx	The number of origin web server responses in the range of 300 to 307 (redirection responses).
33	wamAppStatOws4xx	The number of origin web server responses in the range of 400 to 417 (client errors).
34	wamAppStatOws5xx	The number of origin web server responses in the range of 500 to 505 (server errors).
35	wamAppStatOwsDropped	The number of requests dropped by origin web server.
36	wamAppStatOwsRejected	The number of requests rejected by origin web server.
37	wamAppStatWam2xx	The number of responses in the range of 200 to 206 (successful responses) served by this WebAccelerator application.
38	wamAppStatWam3xx	The number of responses in the range of 300 to 307 (redirection responses) served by this WebAccelerator application.
39	wamAppStatWam4xx	The number of responses in the range of 400 to 417 (client errors) served by this WebAccelerator application.
40	wamAppStatWam5xx	The number of responses in the range of 500 to 505 (server errors) served by this WebAccelerator application.
41	wamAppStatWam503	The number of 503 response served by this WebAccelerator application.
42	wamAppStatWamDropped	The number of requests dropped by this WebAccelerator application.

Installation overview

This document lists very basic steps for installing the software. BIG-IP System: Upgrading Active/Standby Systems and BIG-IP System: Upgrading Active-Active Systems contain details and step-by-step instructions for completing an upgrade.

Installation checklist

Before you begin:

Update/reactivate your system license, if needed, to ensure that you have a valid service check date.
Ensure that your system is running version 10.0.0 or later and is using the volumes formatting scheme.
Download the .iso file (if needed) from F5 Downloads to /shared/images on the source for the operation. (If you need to create this directory, use the exact name /shared/images.)
Configure a management port.
Set the console and system baud rate to 19200, if it is not already.
Log on as an administrator using the management port of the system you want to upgrade.
Boot into an installation location other than the target for the installation.
Save the user configuration set (UCS) in the /var/local/ucs directory on the source installation location, and copy the UCS file to a safe place on another device.
Log on to the standby unit, and only upgrade the active unit after the standby upgrade is satisfactory.
Turn off mirroring.
If you are running WAN Optimization Manager, set provisioning to Minimum.

Installing the software

F5 offers several installation methods. Choose the method that best suits your environment.

Warning: Do not use the --nomoveconfig option described in the following table on systems with existing, running installations of Application Security Manager. Doing so removes all content from the associated database. Instead, ensure that the configuration on the source installation location matches the one on the destination. To do so, save the UCS configuration on the location you want to preserve, and apply that configuration to the destination before or after the installation operation.

To install the software, use one of the methods described here.

Install method	Command
Format for volumes, migrate source configuration to destination	`image2disk --format=volumes <downloaded_filename.iso>`
Format for volumes, preserve destination configuration (for fully 10.x environments)	`image2disk --nomoveconfig --format=volumes <downloaded_filename.iso>`
Install without formatting (not for first-time 10.x installation)	`bigpipe software desired HD.<n.n> version 10.x build <nnnn.n>.iso product BIG-IP`
Format for partitions (for mixed 9.x and 10.x environments)	`image2disk --format=partitions <downloaded_filename.iso>`
Install from the browser-based Configuration utility	Use the Software Management screens in a web browser.

Post-installation tasks

After the installation finishes, you must complete the following steps before the system can pass traffic.

Ensure the system rebooted to the new installation location.
Log on to the browser-based Configuration utility.
Run the Setup utility.
Provision the modules.
Convert any bigpipe scripts to tmsh. (Version 11.0.0 does not support the bigpipe utility.)

Installation tips

The upgrade process installs the software on the inactive installation location that you specify. This process usually takes between three minutes and seven minutes. During the upgrade process, you see messages posted on the screen. For example, you might see a prompt asking whether to upgrade the End User Diagnostics (EUD), depending on the version you have installed. To upgrade the EUD, type yes, otherwise, type no.
You can view a list of the image2disk utility options by running the command image2disk --help.
You can check the status of an active installation operation by running the command watch tmsh show sys software, which runs the show sys software command every two seconds. Pressing Ctrl + C stops the watch feature.
If installation fails, you can view the log file. For image2disk installations, the system logs messages to the file you specify using the --t option. For other installations, the system stores the installation log file as /var/log/liveinstall.log.

Upgrading from earlier versions

Your upgrade process differs depending on the version of software you are currently running. Software version 10.x introduced the ability to run multiple modules based on platform. The number and type of modules that can be run simultaneously is strictly enforced through licensing. For more information, see SOL10288: BIG-IP software and platform support matrix.

Warning: Do not use the 10.x installation methods (the Software Management screens, the b software or tmsh sys software commands, or the image2disk utility) to install/downgrade to 9.x software or operate on partitions. Depending on the operations you perform, doing so might render the system unusable. If you need to downgrade from version 10.x to version 9.x, use the image2disk utility to format the system for partitions, and then use a version 9.x installation method described in the version 9.x release notes to install the version 9.x software.

Upgrading from version 10.x

When you upgrade from version 10.x software, you use the Software Management screens in the Configuration utility to complete these steps. To open the Software Management screens, in the navigation pane of the Configuration utility, expand System, and click Software Management. For information about using the Software Management screens, see the online help.

Upgrading from versions earlier than 10.x

You cannot roll forward a configuration directly to this version from BIG-IP version 4.x, or from BIG-IP versions 9.0.x through 9.6.x. You must be running version 10.x software. For details about upgrading to those versions, see the release notes for the associated release.

Fixes in 11.1.0

This BIG-IP^® WebAccelerator^® release includes all previously released hot fixes.

ID 341520	The WebAccelerator system does not cache content until the second time that the object is seen. If the object is evicted prior to the second time it is seen (due to exceeding the Maximum Entries setting in the profile), then the object will not be cached. If the object is not evicted, then the second time that the entity is encountered it will be cached normally. To disable this functionality on a node and maintain the behavior of earlier versions, use tmsh to set the cache-first-hit option to yes (if not present, the default is no).
ID 357250	An object is now created to indicate that content is uncachable. This reduces resource contention for uncachable content. If the object at the URI becomes cachable again, the object will cache normally.
ID 364611	In the BIG-IP Dashboard under the Web Acceleration View for the Throughput pane, the units for the graphs in the From Cache and Proxied tabs now correctly show the units as Bps (bytes per second) instead of bps (bits per second).
ID 369382	datastor diagnostics are dumped when tmm is halted. When datastor is terminating, it writes a /shared/datastor_terminate.txt file. When wamd is terminating, or when a qkview is taken, the diagnostic is written to /shared/datastor_diag.txt.gz.
ID 371674	In this version, a response will be cached even when the matching node (for the response) has the Always proxy requests setting selected (enabled). To maintain the behavior of previous releases, the migration script maps the Always proxy requests setting to a Maximum Age of zero and the Honor Headers from Origin Web Server setting to disabled.

Fixes in 11.0.0

Bug	Description
ID 224993	On a partitioned system, a virtual server could not be deleted that had an http class with WebAccelerator set to Accelerate at creation time. This issue has been resolved.
ID 344515	When the WebAccelerator module and Application Security Manager are enabled on the same HTTP class, the blocking page is sent to the client and no longer times out.
ID 345983	Requests for expired cached items are not recorded as expired in WebAccelerator Performance Reports if the origin web server response is 304 (Not Modified). Instead, the response is recorded in the Performance Reports as a cache hit. However, if the response from the origin web server is 200 (OK), the response is recorded in the performance reports as expired, and all subsequent re-validations, where the origin web server responds with 304 (Not Modified), are recorded as expired.
ID 351218	Signal handling enhancements simplify WebAccelerator system troubleshooting.
ID 352257	This version does not allow branch nodes to contain an Invalidation Rule. You can only configure Invalidation Rules on child nodes.
ID 352275	The pvac process no longer leaks memory when WebAccelerator policies are reloaded and document invalidations exist.
ID 362941	Users can use all disk space allocated to the WebAccelerator module on systems with RAID drives.
ID 363079	After upgrading from 10.x.x to 11.0.0, you might need to ensure that the origin web server Cache-Control header directives that are selected to be honored are what you expect. For example, IBR on documents with an origin web server Cache-Control Private directive will not work if this origin web server directive is honored in a WebAccelerator policy.
ID 364439	The first request for a PDF file after clearing the cache will no longer bypass the WebAccelerator module.
ID 364997	Datastor now gets more memory for the page cache when the WebAccelerator module is provisioned.
ID 365163	Double quotation marks enclose entity tag (ETag) strings that are created by the WebAccelerator module.

Known issues

This release contains the following known issues.

ID 346062	Symmetric deployment support for the WebAccelerator module is not available in version 11.x.x.
ID 346536	If resources for PDF linearization become unavailable while accepting a PDF file, the linearization and connection to client will abort. No workaround is available; however, if the origin web server supplies Content-Length headers for PDF content, this condition becomes less likely.
ID 348816	When rolling forward a WebAccelerator 10.x configuration to version 11.x.x, access logging configuration on the acceleration policy is not rolled forward. To enable access logging for BIG-IP WebAccelerator version 11.x.x, refer to Using the Request Logging Profile in the WebAccelerator Implementations guide.
ID 353833	When creating a new policy, instead of modifying a predefined policy, nodes are created with the Method parameter on the Variation tab set to Same Content. When creating a new policy, F5 Networks recommends setting the Method parameter on the Variation tab for GET or POST to Different Content.
ID 354758	Modified Lifetime settings for a policy node might not be applied to content already in cache. For example, a cached object that is valid for 7 days will not automatically expire if you change the Lifetime page for its matched node to 300 seconds, or if you choose to honor the origin web server max-age or s-maxage setting. To apply modified policy settings before they expire, invalidate the cache for the applicable application.
ID 354983	Requests for expired cached items are not recorded as expired in WebAccelerator Reports if the origin web server response is 304 (Not Modified). Instead, the response recorded in the Performance Reports as a cache hit. However, if the response from the web server is 200 (OK), the response is recorded in the performance reports as expired, and subsequent re-validations, where the origin web server responds with 304 (Not Modified), recorded as expired.
ID 356245	A COMPRESS::enable or COMPRESS:disable iRule does not take effect on cached items.
ID 356867	Earlier versions of the BIG-IP WebAccelerator module allowed importing of identically named acceleration policies without selecting the Overwrite existing policy of the same name check box, resulting in a number appended to the imported acceleration policy name. In this version, you must select the Overwrite existing policy of the same name check box to import identically named acceleration policies.
ID 356875	During a configuration migration, the BIG-IP version 11.0 software does not issue a warning that Unmapped Hosts elements of the WebAccelerator configuration will be lost when converting a configuration with Unmapped Hosts (forward proxy) options enabled.
ID 357320	For iRules associated with a virtual server that has an associated Web Acceleration profile, [CACHE::disable] can only be used if there is no WebAccelerator Application enabled in the Web Acceleration profile, and [WAM::disable] can only be used if there is a WebAccelerator Application enabled in the Web Acceleration profile. Edit the iRules to use the correct command, either CACHE::disable or WAM::disable, for the virtual server's Web Acceleration profile.
ID 357706	In the BIG-IP Dashboard, in the Web Acceleration view, on the Performance pane, with the Errors tab in focus, the Requests bypassed due to overload graph shows zero statistics because the WebAccelerator module does not bypass traffic due to resource constraints.
ID 357712	The stat field proxied_per_iRule, in the stat table tmctl wam_application_stat, remains at zero.
ID 357736	Matching rules for the Cookie parameter always match the first cookie. Subsequent instances of the same cookie in the request are ignored by matching. To match subsequent instances of the same cookie in the request, create the matching rule to specify the cookie name, and match any value. For example, creating the rule with a regular expression of .* will match if the cookie name is identical and the cookie value is any value.
ID 357906	You cannot add conditions to WebAccelerator policy matching that test for white space.
ID 357921	The Configuration utility should provide a specific error message when an extension or MIME type for an object type is not unique, instead of a generic error message.
ID 358109	Invalidation rules on a given node are only effective in invalidating one single extension.
ID 358530	Various matching parameters in WebAccelerator Configuration utility that contain a regular expression with a pipe symbol (\|) are incorrectly formatted for display.
ID 358698	The WebAccelerator module is not supported on 2GB systems.
ID 358785	The WebAccelerator GUI displays dormant proxy rules on a node even when it is set to Always Proxy.
ID 358802	Version 11.0 does not support symmetric WebAccelerator systems. You must reconfigure symmetric WebAccelerator systems as asymmetric systems before you upgrade them from version 10.x to version 11.0.
ID 358833	For parameter value substitution, the Request URL setting for the source definition type always applies an absolute URL, even though a relative URL is specified.
ID 359062	This version does not include query parameters in a POST body for any rules: matching, variation, proxy, or invalidation.
ID 359089	If you configure a Web Acceleration profile for a virtual server without enabling a WebAccelerator application, an INFLATE hudfilter is unavailable, which will cause DECOMPRESS:: commands to fail.
ID 359093	If you want to receive an HTTP POST request and decompress it before sending it to the origin web server, and the client software sends an Expect: 100-continue header and the HTTP request-chunking mode is set to preserve, the request will not be decompressed. Specifically, the following iRule will not decompress the request in the presence of the Expect header with request-chunking set to preserve: when HTTP_REQUEST { DECOMPRESS::enable } Instead, to receive an HTTP POST request and decompress it before sending it to the origin web server, do one of the following steps: Ensure that the client doesn't send an Expect header. Change the request-chunking to selective, instead of preserve.
ID 359498	In TMSH, the WebAccelerator module can assemble hostnames that include IP addresses with MultiConnect prefixes, for example, wa1.10.0.0.1. In TMSH, specify zero (0) for the number of HTTP and HTTPS subdomains on any WebAccelerator hostnames that are IP addresses.
ID 359647	For version 11.x.x, during configuration upgrades, the software does not warn users that URL normalization and normalization-related elements of the configuration will be lost. No workaround for this issue is available.
ID 360211	Invalidation rules that use components not in the UCI might not invalidate content if it is accessed without those components before it is accessed with those components.
ID 360488	Using the Configuration utility to make changes to the WebAccelerator configuration, such as deleting an Acceleration Policy or Object Type, might take up to 30 seconds to write to disk. This process can result in deleted objects reappearing in the configuration if it is reloaded immediately after making the change.
ID 361618	When an MCPD communication failure occurs, the WebAccelerator wamd process does not automatically restart. There is no workaround for this issue.
ID 361671	Cache-Control field names are truncated to 16 characters in length. Log message not written out when field names for Cache-Control headers are truncated.
ID 361810	If two invalidation rules match the same path but have different extensions, one will match and one will not.
ID 361852	Invalidation rules that specify cached content by protocol invalidate content regardless of the protocol.
ID 361869	An invalidation rule that specifies Client IP as a condition for invalidation never matches. The trigger can match an IP; however, the content to invalidate cannot match.
ID 361875	An invalidation rule that specifies an empty or absent Query Parameter for Cached Content to Invalidate is not functional. This invalidation rule works, however, if you specify a non-empty Query Parameter value for Cached Content to Invalidate.
ID 361982	Some combinations of spaces and tabs, before and after HTTP header values, are not properly ignored and defeat invalidation that is based on those headers.
ID 362005	A message needs to be logged when the Cache-Control header is truncated to a maximum length of 256 characters.
ID 362275	Setting the Web Acceleration profile to optimized-acceleration for a virtual server without enabling a WebAccelerator Application will result in an error message similar to the following: cache memory assigned to Web Acceleration profiles (6144MB) exceeds the maximum amount (697MB) defined by Ramcache.MaxMemoryPercent (50). The optimized-acceleration profile is designed for use with the WebAccelerator module. If you are not using the WebAccelerator module with your virtual server and wish to use standard cache, you should use the optimized-caching profile, or create a customized Web Acceleration profile that uses either the optimized-caching profile or basic webacceleration profile as the parent.
ID 362862	During the period after cached content expires according to client cache-control directive values for min-fresh or max-age, and before cached content expires according to the WebAccelerator lifetime settings, requests are proxied to the origin web server. For these requests, if standin codes are provided by the origin web server, the standin period is not invoked.
ID 363059	Renaming a top-level policy node may cause an unintended reordering of policy nodes, resulting in a different prioritization of matching criteria.
ID 363079	After upgrading from 10.x.x to 11.x.x, you might need to ensure that the origin web server Cache-Control header directives that are selected to be honored are what you expect. For example, IBR on documents with an origin web server Cache-Control Private directive will not work if this origin web server directive is honored in a WebAccelerator policy.
ID 363171	Validation of Web Acceleration profiles can fail during a config sync when the sum of the cache sizes exceeds the Datastor volume size on the receiving BIG-IP system. For all BIG-IP systems in the Device Group: Run each BIG-IP system with identical provisioning. Ensure that each BIG-IP system has the same volume size for Datastor: `# tmsh show sys disk application-volume datastor`. Configure the Web Acceleration profiles. Sync each BIG-IP system to the Device Group.
ID 363402	Specifying content to invalidate as the Referer header from the invalidation trigger (which specifies request-data-type referrer) is not functional.
ID 363413	Specifying content to invalidate as the User-Agent header from the invalidation trigger (which specifies request-data-type user-agent) is not functional.
ID 363699	The WebAccelerator module Configuration utility incorrectly allows creation of nodes with reserved keyword names, which results in the configuration improperly loading the next time that the unit is rebooted or the configuration is loaded. This issue also causes config sync in a High Availability pair to fail. When creating WebAccelerator policy node names in the Configuration utility, avoid using the following reserved keywords. invalidations matching order proxy substitutions variation code description
ID 363845	After changing the compression mode on a custom object type, a full GET request, for compressed content that matches a node with this custom object type, gets a 304 (Not Modified) response. After changing the compression setting on object-types, you need to clear the cache: `# tmsh delete ltm profile wa-cache all` This command clears the cache at the cost of losing the cache contents, causing some requests to return to the origin web server.
ID 363994	The WebAccelerator module responds with a 416 (Requested Range Not Satisfiable) status code for requests with byte ranges that have an end value that exceeds the resource length.
ID 364338	The WebAccelerator module allows the creation of Object Types that contain a space in the identifier name on the Object Types page in the Configuration utility and by using TMSH. Including a space prevents the ability to delete the object type from the Configuration utility. When you create an identifier name for an object type from the Configuration utility or in TMSH, do not include a space in the name.
ID 364603	For this version, in the BIG-IP Dashboard, in the Web Acceleration view, on the Cache pane, with the Entries tab in focus, the graph displays an incorrect value. The graph displays the number of cache transactions per second, instead of displaying the number of entries in cache.
ID 364615	In the BIG-IP Dashboard, in the Web Acceleration view, all graphs with the 5 minutes tab selected might display data with a greater value than the actual value. In the BIG-IP Dashboard, in the Web Acceleration view, to display data that is more accurate than the 5 minutes tab, click a tab with a different period, for example, the 3 Hours tab.
ID 365310	Some metadata may not be cleared by using the wa_clear_cache command. This issue is fixed.
ID 365337	The WebAccelerator module does not add an Accept-Ranges header to the response when the cache misses (S code 10201).
ID 365374	When an invalid hostname is specified in the Requested Host field for a WebAccelerator application, the selected policy in the Policy list box reverts to Select One. Do one of the following steps to work around this issue. In the Policy list, select a policy. Click Cancel.
ID 365487	For this version, in the BIG-IP Dashboard, in the Web Acceleration view, on the Performance pane, with the From cache tab in focus, the 5 minutes time interval shows waveforms with levels that need to be scaled correctly.
ID 365492	For this version, in the BIG-IP Dashboard, in the Web Acceleration view, on the Throughput pane, with the Throughput tab in focus, the 5 minutes time interval shows waveforms with levels that need to be scaled correctly.
ID 365585	If a Web Acceleration profile is used by a virtual server and the cache size for the Web Acceleration profile is set to zero, the Traffic Management Microkernel (TMM) will crash. Either delete the Web Acceleration profile or set the cache size to a value of 1 or greater.
ID 365600	In the BIG-IP Dashboard, in the Web Acceleration view, reporting of statistics shows spikes at irregular intervals with a magnitude of 2 to 3 times the average traffic through the WebAccelerator module. This was observed for the 5-min interval window.
ID 368808	For this version, when a user who is assigned to an Acceleration Policy Editor role receives access to a partition other than common, then that user cannot create WebAccelerator policy object types for use in that role's policy.

Contacting F5 Networks

Phone:	(206) 272-6888
Fax:	(206) 272-6802
Web:	http://support.f5.com
Email:	support@f5.com

For additional information, please visit http://www.f5.com.

Legal notices

Was this resource helpful in solving your issue?

Yes - this resource was helpful
No - this resource was not helpful
I don‘t know yet

NOTE: Please do not provide personal information.

Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)

Reload Audio Image Help