jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From buckett <...@git.apache.org>
Subject [GitHub] jmeter pull request #347: Supply Subject Alternative Name on HTTPS certs.
Date Fri, 01 Dec 2017 14:53:49 GMT
GitHub user buckett opened a pull request:

    https://github.com/apache/jmeter/pull/347

    Supply Subject Alternative Name on HTTPS certs.

    Recently browsers have started to not trust a certificate if it doesn’t have a Subject
Alternative Name (SAN) that matches the domain name. This causes the HTTPS proxy to generate
warnings in the browser even if the CA certificate is trusted.
    
    This sets the SAN on all the certificates that are generated so that the browsers trust
them.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/buckett/jmeter subject-alt-name

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jmeter/pull/347.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #347
    
----
commit b1145e5930c5d7298f33f661099356d3aa7e7ddb
Author: Matthew Buckett <matthew.buckett@it.ox.ac.uk>
Date:   2017-12-01T14:50:37Z

    Supply Subject Alternative Name on HTTPS certs.
    
    Recently browsers have started to not trust a certificate if it doesn’t have a Subject
Alternative Name (SAN) that matches the domain name. This causes the HTTPS proxy to generate
warnings in the browser even if the CA certificate is trusted.
    
    This sets the SAN on all the certificates that are generated so that the browsers trust
them.

----


---

Mime
View raw message