jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: For the next release
Date Sat, 25 Aug 2012 14:28:33 GMT
Hello sebb,
I agree with all your propositions, it's true we always have these kind of
questions in user list.
 But maybe we should test that a) does not break existing test plan that
may have saved proxy under testfragment (hack but possible)
Regards
Philippe

On Saturday, August 25, 2012, Milamber wrote:

> Hello,
>
> For the next release, I propose:
>
> a) Since JMeter 2.4 and the capabilities to record HTTPS request by JMeter
> proxy, I propose to remove the options "Attempt HTTPS Spoofing" and "Only
> spoof URLS matching" on the HTTP Proxy Server element.
>
> b1) renew the JMeter self-certificat (current expire date is 2014-08-04,
> to a long period (20 years)
> b2) Extract from the file proxyserver.jks the public (fake) key Apache
> JMeter to a PEM format, in a file "proxyserver.pem".
> b3) Add some sentences in the proxy documentation to invite the user to
> add this public key as  a trusted CA in their browser or OS's certificat
> manager to permit the recording of a https session with JMeter proxy (and
> remove it at the end of record). (or Accept temporary the certificate from
> the browser)
>
> c) Make HTTPClient 3.1 to the default HTTP Request (and Proxy generated
> request)
>
> If you are OK, I can make the changes for this points.
>
> Thanks in advance for your feedback or your agree.
>
> Milamber
>


-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message