jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: JMeter nightly build and recording
Date Thu, 03 Oct 2013 12:45:42 GMT
On 1 October 2013 22:14, Philippe Mouawad <philippe.mouawad@gmail.com> wrote:
> Hello,
> Testing new Proxy recording on github, I finally managed to record but this
> time it was not as easy as for other websites:
>
> I finally succeeded by calling in browser:
> - https://ssl.fastly.net and accepting jmeter certificate
> - collector.githubapp.com and accepting jmeter certificate
>
> Just adding this in HTTPS Domain was not enough:
> github.global.ssl.fastly.net,*.github.com,github.global.ssl.fastly.net,
> collector.githubapp.com,ssl.google-analytics.com

Why not use domains for them all?

*.fastly.net
*.github.com
*.githubapp.com
*.google-analytics.com

> Is this what was expected ?
> I would have thought accepting JMeter CA would be enough
>
> Am I missing something ?

Presumably.

What URLs did you visit?

What does the jmeter log say?
It should report warnings for missing certificates; if no extra logs
or changed levels may be needed.

> By the way, before release we need to finish this:
> - Document the changes made on JMeter Proxy Server
> - Rename it
> - Update screenshots for changes and maybe reference documentation
>
> Regards
> Philippe

Mime
View raw message