Bug 61748 - Add ability to send compressed request
Summary: Add ability to send compressed request
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 3.3
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2017-11-11 22:47 UTC by Philippe Mouawad
Modified: 2018-05-07 15:41 UTC (History)
1 user (show)

Patch implementing option 1 (3.49 KB, patch)
2018-05-07 15:41 UTC, UbikLoadPack support
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2017-11-11 22:47:15 UTC
We should provide a way to send compressed content.

We could detect if a header is set :
- Content-Encoding: gzip

And compress the body as a consequence
Comment 1 UbikLoadPack support 2018-05-07 15:41:07 UTC
Created attachment 35914 [details]
Patch implementing option 1

As per dev mailing list discussion:

In some applications, the request body needs to be gzipped.

It is currently possible to do it by developping a JSR223 PreProcessor but it requires some development knowledge.

We would like to contribute a patch to provide this but have some questions on what best options would be:

    Option 1 :Should it be automatic, ie, whenever a Header Content-Encoding=gzip , we do it:
        To disable it, remove Content-Encoding header
        Is there a case where it would be annoying ?
        We would add a property to disable registration of this Interceptor to disable globally the feature if really needed
    Option 2 :Should it be activated by a checkbox in HTTP Request Advanced Tab ?
        Yet Another option in a complex UI ?
    Option 3 : Should it be a PreProcessor ?:
        More flexible
        but  requires insertions in many places

Unless there is a case we would go for Option 1.

Any thoughts ?

UbikLoadPack Team