Re: HttpClient SSL Handshake and self-signed certificate

Thanks Steven. That's just what I was looking for. On 30 October 2016 at 23:21, Steven Swor wrote: > Hi Stuart, > > The options you're looking for are at > http://jmeter.apache.org/usermanual/get-started.html#proxy_server > > Note that, for whatever reason, Sun

Re: HttpClient SSL Handshake and self-signed certificate

Hi Stuart, The options you're looking for are at http://jmeter.apache.org/usermanual/get-started.html#proxy_server Note that, for whatever reason, Sun decided it was a good idea to separate non-proxy hosts by a pipe character instead of a comma, so if you're running on a non-Windows system,

Re: HttpClient SSL Handshake and self-signed certificate

Hi can you clarify what you mean. The JMeter Proxy is used for recording a script - as such the browser needs to be configured to send all requests to JMeter for it to record it - you typically dont want to exclude things here (if you did , you'd configure the browser to bypass the JMeter proxy

Re: HttpClient SSL Handshake and self-signed certificate

Hi Ivan, Thanks for your reply and the suggestions. I did give them all a try but none worked. I eventually figured out what the problem is but might still need some advice on how to handle it. There's an HTTP proxy in place in the intranet I work on and the website I'm testing goes through

Re: HttpClient SSL Handshake and self-signed certificate

hi, No idea whether JMeter validates the hostname. I thought not, as I have some tests that access the server by IP address, and the server certificate has a hostname. A couple of ideas to try to narrow down the problem - check jmeter.log You should see some INFO entries from