On Sun, 2016-05-01 at 17:22 +0200, Philippe Mouawad wrote:
> Hi Oleg,
> I understand, but in our particular case users want to have information
> about original response headers.
>
Why do not just disable content decompression if it is not needed?
Oleg
> Does this way of implementing it look
On Fri, 2016-04-29 at 14:51 +0200, NGUYEN-VIET Quang wrote:
> Hello,
>
> We use httpclient 4.1. ( we plan to upgrade soon)
>
> Juste a simple question about how connection pool behave when we change
> maxTotal on fly, without releasing connetions in use. ( with
> releaseConnection() for
Hi,
Because during load testing you want:
- to simulate browser behaviour, in a lot of case compression will be
enabled
- user will want to check server returns compressed response and also have
information about response sizes compressed which is the real traffic
taking place
- but then user will
On Sun, 2016-05-01 at 16:08 +0200, Philippe Mouawad wrote:
> Hello,
> We have a regression report in JMeter 3.0 due to what seems to be a new
> behaviour of HttpClient 4.5.2, introduced on Feb 25, 2014 by:
>
>-
>
>
On Sun, 2016-05-01 at 17:41 +0200, Philippe Mouawad wrote:
> Hi,
> Because during load testing you want:
> - to simulate browser behaviour, in a lot of case compression will be
> enabled
> - user will want to check server returns compressed response and also have
> information about response sizes
Hi Oleg,
I understand, but in our particular case users want to have information
about original response headers.
Does this way of implementing it look ok to you:
- https://bz.apache.org/bugzilla/attachment.cgi?id=33817=diff
Or can it break something in HttpClient ?
Thanks
Regards
On Sun,
Hello,
We have a regression report in JMeter 3.0 due to what seems to be a new
behaviour of HttpClient 4.5.2, introduced on Feb 25, 2014 by:
-
https://github.com/apache/httpclient/commit/5d11a3e751fe0c02a7a4539d3436b06e0be35876#diff-c54e3439558bee75dd7e2953280a7e08
As per following
