- Upgrade netty to 4.1.115 #183
- Correctly log the state of
ssl_enabled
duringrun
#180
- Netty boss and worker groups are separated #178 As a result, when shutdown requested incoming connections are closed first and improved graceful shutdown
- bump netty to 4.1.109 #173
- Fixed SSL Java KeyStore support #171
- Added
ssl_keystore_type
configuration - Added SSL Java TrustStore configurations (
ssl_truststore_type
,ssl_truststore_path
andssl_truststore_password
)
- bump netty to 4.1.100 #170
- bump netty to 4.1.94 #167
- bump netty to 4.1.93 #166
- Reviewed and deprecated SSL settings to comply with Logstash's naming convention #165
- Deprecated
ssl
in favor ofssl_enabled
- Deprecated
ssl_verify_mode
in favor ofssl_client_authentication
- Deprecated
keystore
in favor ofssl_keystore_path
- Deprecated
keystore_password
in favor ofssl_keystore_password
- Deprecated
- Update Netty dependency to 4.1.87 #162
- Feat: review and deprecate ssl protocol/cipher related settings #151
- Fix: codecs provided with
additional_codecs
now correctly run in the pipeline's context, which means that they respect thepipeline.ecs_compatibility
setting #152
- Feat: TLSv1.3 support #146
- Build: do not package log4j-api dependency #149. Logstash provides the log4j framework and the dependency is not needed except testing and compiling.
- Update log4j dependency to 2.17.0
- Update log4j dependency to 2.15.0
- Fix: update to Gradle 7 #145
- Docs: added
v8
as an acceptable value forecs_compatibility
#142
- Changed jar dependencies to reflect newer versions #140
- Add ECS support, mapping Http header to ECS compatible fields #137
- Feat: improved error handling/logging/unwraping #133
- Fixes a regression introduced in 3.1.0's migration to the Netty back-end that broke some users'
browser-based workflows. When an instance of this plugin that is configured to require Basic
authentication receives a request that does not include authentication, it now appropriately
includes an
WWW-Authenticate
header in its401 Unauthorized
response, allowing the browser to collect credentials before retrying the request.
- Updated jackson databind and Netty dependencies. Additionally, this release removes the dependency on
tcnative
+boringssl
, using JVM supplied ciphers instead. This may result in fewer ciphers being available if the JCE unlimited strength jurisdiction policy is not installed. (This policy is installed by default on versions of the JDK from u161 onwards)#126
- Refactor: scope (and avoid unused) java imports #124
- Revert updates to netty and tcnative since CBC ciphers are still used in many contexts
- More about the reasoning can be found here
- Update netty and tcnative dependency #118
- Added 201 to valid response codes #114
- Documented response_code option
- Added configurable response code option #103
- Added explanation about operation order of codec and additional_codecs #104
- Loosen jar-dependencies manager gem dependency to allow plugin to work with JRubies that include a later version.
- Changed jar dependencies to reflect newer versions
- Fix some edge cases of the verify_mode+ssl_verify_mode options
- Fix expensive SslContext creation per connection #93
- Add
request_headers_target_field
andremote_host_target_field
configuration options with default tohost
andheaders
respectively #68 - Sanitize content-type header with getMimeType #87
- Move most message handling code to java #85
- Fix: respond with correct http protocol version #84
- Replace Puma web server with Netty
- Support crt/key certificates
- Deprecates jks support
- Docs: Set the default_codec doc attribute.
- Make sure default codec is also cloned for thread safety. #80
- Always flush codec after each request and codec decoding. #81
- In the event that all webserver threads are busy this plugin will now return a 429, busy, error.
- Update gemspec summary
- Fix some documentation issues
- Improve error logging to log more details, including stack trace, for true bugs. This makes debugging broken codecs much easier.
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Use a new class as redefined Puma::Server class as we need to mock one method and only need it for this plugin, but not for all parts using puma in logstash.Fixes #51.
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Bump puma dependency to 2.16.0
- Support for custom response headers
- Support compressed and gziped requests (thanks dwapstra)
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0
- Include remote host address to events (#25)
- Fix for missing base64 require which was crashing Logstash (#17)
- First version: New input to receive HTTP requests
- Added basic authentication and SSL support