- 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. logstash-plugins#80
- Always flush codec after each request and codec decoding. logstash-plugins#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 logstash-plugins#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