Need understanding of HTTP compression profile.
Hi, I have question with HTTP Compression profile. My LTM running on 12.1.2 where HTTP Compression enable on one of the Virtual Server serving web requests. Web administrator requested us to perform compression on LTM for specific URI only so we added few URI in list. i.e. URL is , we have added /test in URI List. Content Compression is selected as "Not Configured". So my question is Whether compression works on not? If it works, it will compress all the content type served under /test/* ? How LTM behaves for content already received from server in compressed form? Very limited knowledge with compression hence need some inputs. I have read F5 online article but still need some clarification. https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-profiles-reference-11-6-0/3.htmlunique_1659057140 Thanks in advance. Mihir
Unable to add 7200v to a sync-group - HTTP compression license error
Landscape: EXISTING: 3600 x 2 in HA, Sync and Failover group. Both running 11.4.1.HF2 with LTM, APM provisioned. NEW : Trying to add a new 7200v to the sync and failover group. New 7200 running same 11.4.1.HF2 with LTM, APM provisioned. Plan is to add 7200v into existing sync-and-failover group; once synced will decommission 3600s. DONE SO far: Added the devices to each other - build device trust among each other - they are both able to see each other through network - no issues. ISSUE: Everytime I run sync-and-failover config - it syncs the Admin and root passwords and thereafter fails with error message on LTM7200 "Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: log.pva.level is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: mapi.discover.exchange.server is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: md.enablemaxandglobalhttpstats is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: md.maxcspminjectionratio0 is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: md.maxcspminjectionratio1 is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: Per-invocation log rate exceeded; throttling. Jun 7 12:04:54 LTM7200v err mcpd[7391]: 01070356:3: HTTP compression feature not licensed. Jun 7 12:04:54 LTM7200v err mcpd[7391]: 01071488:3: Remote transaction for device group /Common/SYNC-And-Failover to commit id 23 6022032392778850511 /Common/LTM3600-1 0 failed with error 01070356:3: HTTP compression feature not licensed.. BIPGIP7200 has the BEST license enabled which has almost what is required for it to function. But there is no exclusive mention of HTTP Compression license Any suggestions?
11.6 HTTP compression limit
Hi Guys, I have the default http compression license which provides me compression up to 50mbits, the thing is, I am using maximum 3Mbit/sec of http compression throughput (checking with statistics, it clear show plataform limit 1Gbps, License limit 48Mbps, Current Value 3Mbps, and checking the graph it never go beyond 20Mbps) but I am still getting the following message: Compression license limit of 50 Mbit/s exceeded today. How does this limit works? I thought that as far as I don't cross the 50Mbit/sec limit it should be fine, so I don't know why I am getting this error with only 3Mbit/sec throughput. Can someone help me to understand this? Thanks a lot!Selective Pass-through
Hello, I need to inject data into some webpages using an iRule. The backend-server sends HTTP data chunked and compressed (gzip). However, only some pages need to be injected into. Those can be identified by an HTTP-Header (and only this way). I also need all outgoing traffic to be chunked and compressed and with working keep-alive connections. I got this working by setting Response Chunking and Compression to Selective and perform the injection itself in an iRule using STREAM::expression . The problem however is that all data is being decompressed (and in turn rechunked) by the f5, as soon as the compression module is not set to Disabled . This induces an unnecessarily high load on the f5, which I'd like to avoid. What I want is to identify the header in the response from the backend-server, if found inject, rechunk and recompress; otherwise completely pass-through all HTTP data without processing anything. Setting the compression module to Disabled seems to be unfeasible, since I can't perform an injection anymore. Using COMPRESS::disable disables compression, not the compression module, thus decompressing everything from the server and sending it uncompressed to the client. After fiddling around a bit, it seems that compression can be disabled implicitly by disabling HTTP processing ( HTTP::disable ). But this seems to be incompatible with keep-alive connections (because the next request on the same connection isn't recognized). And now I ran out of ideas and ask here: is there any way to archive a selective pass-through, depending on a header sent by the backend-server? I am using BIG-IP 10.2.4 Build 577.0 Final. We are thinking about switching to 11 in the mid-term, but a solution for 10 would be nice. Thanks, Christian