Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.212.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAH9fUpY37dQ9Jdgon27xA_P2-cingFS6OrErHWgamnfpSmbZmQ@mail.gmail.com>
References: 
 <CAH9fUpY37dQ9Jdgon27xA_P2-cingFS6OrErHWgamnfpSmbZmQ@mail.gmail.com>
Date: Thu, 3 Oct 2013 13:45:42 +0100
Message-ID: 
 <CAOGo0VZWJyx3vpfhyQR6W7FZNDDKBFc_m+zw0Vnuqb5Qn0UeAQ@mail.gmail.com>
Subject: Re: JMeter nightly build and recording
From: sebb <sebbaz@gmail.com>
To: dev@jmeter.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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