Release Notes - NGINX agent
- 29 Sep 2022
- 1 Minute to read
- PDF
Release Notes - NGINX agent
- Updated on 29 Sep 2022
- 1 Minute to read
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
0.1.72 - 26th September
Traceable's NGINX agent 0.1.72 release has the following updates:
- Support for new NGINX versions - Traceable's NGINX agent 0.1.72 supports NGINX's versions 1.21.5, 1.21.6, 1.22.0, 1.23.0, and 1.23.1.
- multipart/form-data support - Traceable's NGINX agent 0.1.72 supports
multipart/form-data
. Configure thecapture_content_types
directive in thetraceableai
block. Note thatmultipart/form-data
support requires Traceable's Platform agent 1.24.0.
0.1.71 - 11th August
Traceable's NGINX agent 0.1.71 release has the following updates:
- XML body capture - Traceable's NGINX agent 0.1.71 release provides an option to capture XML request body. Configure the
capture_content_types
directive in thetraceableai
block. For more information, see NGINX Plus or NGINX Community topic. - Configurable blocking status code - You can configure a status code that you wish in the 4xx series when a request is blocked. The default value is 403. Use the
blocking_status_code
directive in thetraceableai
section to configure a custom error code. For more information, see NGINX Plus or NGINX Community topic. - Blocking on Alpine Linux - Traceable's NGINX agent 0.1.71 release supports blocking on Alpine Linux 3.9 and later. You would need Traceable Platform agent 1.21.2 or later for blocking support on Alpine Linux. Also, make sure that
libstdc++
is installed on Alpine Linux. - NGINX crash fix - Traceable's NGINX agent 0.1.71 release provides a fix for a possible NGINX crash when reading a request body from a file.
0.1.70 - 20th April
Traceable's NGINX tracing agent 0.1.7.0 fixes an SSL error with custom-built NGINX running on Amazon Linux.
0.1.69 - 16th March
Traceable's NGINX tracing agent 0.1.69 fixes a potential issue of incoming trace context headers.
0.1.68 - 8th March
Traceable's NGINX tracing agent 0.1.68 fixes an issue that could lead to a crash at startup when blocking was disabled.
Was this article helpful?