The following are released versions of the BlazeMeter API Monitoring Radar Agent (formerly Runscope Radar):
| Version | Release Date |
| 1.11 (current, latest) | Jan 30, 2023 |
| 1.10 | Nov 3, 2022 |
| 1.9 | Oct 21, 2022 |
| 1.8rc | Jun 13, 2022 |
| 1.6rc | Jan 18, 2022 |
| 1.5rc | Jan 5, 2022 |
| 1.4rc | Dec 21, 2021 |
| 1.3rc | Nov 11, 2021 |
| 1.2rc | Oct 5, 2021 |
| 1.1rc | Sep 30, 2021 |
| 1.0rc | Sep 28, 2021 |
What's New in 1.11
HTTP/2 Support
Radar agents starting with version 1.11 support the use of HTTP/2 when performing test requests. The HTTP version used when performing a test request can be configured in the environment behavior settings associated with your test. By default, HTTP/1 only is enabled.
For more details, see API Monitoring Test Behaviors.
Force h2c (HTTP/2 over cleartext)
Radar agents starting with version 1.11 support forcing the use of HTTP/2 over cleartext, also known as h2c. This is useful for test requests that use URLs with the HTTP scheme to access servers that expect HTTP/2 traffic. This can be configured in the environment behavior settings associated with your test. By default, this is disabled.
For more details, see API Monitoring Test Behaviors.
What's New in 1.10
Use of Hostname in HTTP/S Proxy Connection
When connecting through a HTTP/S proxy, the hostname of a test request URL is now properly used, instead of the IP address of the hostname resolved through DNS.
What's New in 1.9
Radar Agent Version Shown for Each Location
You can now view the radar agent version running on each of your locations, as shown in the following example:
To view the version of your radar agent, navigate to test Steps > Request.
Option to Disable DNS Pre-Check
You have the option to disable DNS pre-checks by using the disable-dns-lookup command line flag or config file option. See Radar Agent Overview and Radar Agent Connection Errors.
Built Using Golang 1.19.1
Radar agents are now compiled using Golang 1.19.1 to support security and infrastructure upgrades.
Removed Support for HTTPS Common Name field in X509 Certificates
The HTTPS Common Name (CN) field is no longer supported as of 1.9rc. For more information and how to work around the issue, see Radar Agent Support for HTTPS Common Name in X509 Certificates.
What's New in 1.8rc
Support for TLS 1.3
The Radar agent now supports TLS versions 1.0 through 1.3.
Built Using Golang 1.16.15
In order to support TLS 1.3, Radar agents are now compiled using Golang 1.16.15.
Restriction: Limitation of older X509 Certificates (1.8rc only)
Starting with Golang 1.15, support for X509 certificates that use a legacy CN (common name) field without a SAN extension entry (Subject Alternative Name) has been removed.
If the Radar agent encounters a HTTPS server that uses this type of X509 certificate, the following error will occur:
x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0
You can allow X509 certificates without a SAN entry to be trusted by adding the value x509ignoreCN=0 to the GODEBUG environment variable and restart your Radar agent:
export GODEBUG=x509ignoreCN=0
0 Comments