[Bug 61748] New: Add ability to send compressed request

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61748

            Bug ID: 61748
           Summary: Add ability to send compressed request
           Product: JMeter
           Version: 3.3
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: p.mouawad@ubik-ingenierie.com
  Target Milestone: ---

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61748] Add ability to send compressed request

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61748

UbikLoadPack support <su...@ubikloadpack.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |support@ubikloadpack.com

--- Comment #1 from UbikLoadPack support <su...@ubikloadpack.com> ---
Created attachment 35914
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35914&action=edit
Patch implementing option 1

As per dev mailing list discussion:

-----------------------------------------------------------------
Hello,
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:
        Easy
        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 ?


Thanks
Regards
UbikLoadPack Team
-----------------------------------------------------------------

-- 
You are receiving this mail because:
You are the assignee for the bug.