Forum Discussion
NimbostratusHTTP compression profile and Content-Length header
I have an HTTP profile setup on one of my VS (LTM version 10.2.4), and it looks like sometimes the response to the client does not contain the Content-Length header specifying the compressed size. This is causing us some issues with our custom clients, so is there a way to force the device to always send the Content-Length header?
There is this setting in the profile called "Compression Buffer Size" and the description is "Specifies the maximum number of compressed bytes that the system buffers before inserting a Content-Length header (which specifies the compressed size) into the response. The default is 4096 bytes." and it is set to 4096 right now. I read that statement like 20 times and I don't understand what it is trying to say. I think it may be related to my problem though. Is it saying that if the number of compressed bytes is less than 4096 it will NOT put the Content-Length header at all? It seems very odd for the device to decide to not write out the header only if size is a certain thing.
Thanks!
1 Reply
What_Lies_Bene1Cirrostratus
The responses are probably Chunked. See here for details: http://en.wikipedia.org/wiki/Chunked_transfer_encoding.
You can prevent this (and ensure a Content-Length header is sent) by change the Chunk setting in the related HTTP profile to Unchunk. Note however this may have an impact on performance and you should test carefully.
