Forum Discussion

gates2010_25250's avatar
gates2010_25250
Icon for Nimbostratus rankNimbostratus
Apr 02, 2016
Solved

"Could not uncompress compressed request content" error

Hi, I have a LTM (v10.2.4) setup to handle the following:

Client ---- (HTTPS POST with compressed payload) ---> F5 ------- (HTTP decompressed payload) -----> Pool member

When client sends compressed payload, there are no issues.

When client sends un-compressed payload (json), the f5 returns the below error: "uncompressRequest caught exception: \"message\" = \"Could not uncompress compressed request content"

Is there a way to configure F5 to handle both compressed and uncompressed payload at the same time.

I believe the 'Profile' for 'HTTP' is handling this and this is the custom http profile that I have:

profile http http_custom1 {
    defaults from http
    insert xforwarded for enable
    }

Here are the headers in https POST:

    x-generic-protocol-version: 1.0
    Accept: application/json
    Accept: application/json
    content-encoding: gzip
    content-type: application/json
    Accept-Encoding: gzip

Thank you for your time.

  • This question can be closed. Additional checks showed that F5 is actually NOT decompressing the payload, wireshark displays the compressed payload with a compression header and unzip'd contents hence the confusion.

     

1 Reply

  • This question can be closed. Additional checks showed that F5 is actually NOT decompressing the payload, wireshark displays the compressed payload with a compression header and unzip'd contents hence the confusion.