logstash-input-http 3.4.1-java → 3.4.2-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a988f67d331d96dcc9f9924c4d75d0f840d62ceed3179e74c7e090fbffd824af
-  data.tar.gz: 7b2cb03cdd41413850042a774e6a551e7485e1b6432548c631bb94258517f993
+  metadata.gz: 617f443ab23cb2aa875de1b20cd2476d9696f76f08a2ecfc3820538e5696679c
+  data.tar.gz: 338b0608a20ee0d4c647b5ae3db3bec4d032c5486f3436dc93f361e96c652e0c
 SHA512:
-  metadata.gz: '0885c495ffa29eed33309b5076b21f49cc5e425394d6c0e97f67ed88b1f5a9e4b05d24c16fb8dddb9d03f672d797b8df2b8be3a508b2ff89510e34b17f5d88d9'
-  data.tar.gz: 8466260d37fe5c4e59c24d307400e803b2d83288540eb9a0e7f00af4c4bed4528f4c69ca2b81ea686088c48e0ab2845e03cc98c87c2e00c20f03d8598cf3bf47
+  metadata.gz: ed34be2f84eeac7372e40f68996dce79667a7a2e776a758ca2d8e7b2b95b0c71298290aa222c537101d3784e82fd9063ce5b7a6647c1164c0e311c47124a13c2
+  data.tar.gz: 0c84e4d9793a07a7f500a9345fac0ee1ec969e4e0b5758a316f485c6584dd84001913806d30de2aa005cdec7262ef05bcb616407e5b46d6b6967842a1203323a

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 3.4.2
+ - Docs: added `v8` as an acceptible value for `ecs_compatibility`
+
 ## 3.4.1
  - Changed jar dependencies to reflect newer versions [#140](https://github.com/logstash-plugins/logstash-input-http/pull/140)
 

data/VERSION

@@ -1 +1 @@
-3.4.1
+3.4.2

data/docs/index.asciidoc

@@ -41,7 +41,7 @@ When ECS is enabled, we can ensure a pipeline maintains access to this metadata
 Here’s how ECS compatibility mode affects output.
 [cols="<l,<l,e,<e"]
 |=======================================================================
-| ECS disabled | ECS v1 | Availability | Description
+| ECS `disabled` | ECS `v1`,`v8` | Availability | Description
 
 | [host] | [host][ip] | Always | Host IP address
 | [headers] | [@metadata][input][http][request][headers] | Always | Complete HTTP headers
@@ -144,7 +144,7 @@ The list of ciphers suite to use, listed by priorities.
 * Value type is <<string,string>>
 * Supported values are:
 ** `disabled`: unstructured connection metadata added at root level
-** `v1`: headers added under `[@metadata][http][header]`. Some are copied to structured ECS fields `http`, `url`, `user_agent` and `host`
+** `v1`,`v8`: headers added under `[@metadata][http][header]`. Some are copied to structured ECS fields `http`, `url`, `user_agent` and `host`
 
 Controls this plugin's compatibility with the
 {ecs-ref}[Elastic Common Schema (ECS)].

data/lib/logstash-input-http_jars.rb

@@ -3,4 +3,4 @@
 require 'jar_dependencies'
 require_jar('io.netty', 'netty-all', '4.1.65.Final')
 require_jar('org.apache.logging.log4j', 'log4j-api', '2.11.1')
-require_jar('org.logstash.plugins.input.http', 'logstash-input-http', '3.4.1')
+require_jar('org.logstash.plugins.input.http', 'logstash-input-http', '3.4.2')

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-input-http
 version: !ruby/object:Gem::Version
-  version: 3.4.1
+  version: 3.4.2
 platform: java
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-06-18 00:00:00.000000000 Z
+date: 2021-09-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -160,7 +160,7 @@ files:
 - spec/inputs/http_spec.rb
 - vendor/jar-dependencies/io/netty/netty-all/4.1.65.Final/netty-all-4.1.65.Final.jar
 - vendor/jar-dependencies/org/apache/logging/log4j/log4j-api/2.11.1/log4j-api-2.11.1.jar
-- vendor/jar-dependencies/org/logstash/plugins/input/http/logstash-input-http/3.4.1/logstash-input-http-3.4.1.jar
+- vendor/jar-dependencies/org/logstash/plugins/input/http/logstash-input-http/3.4.2/logstash-input-http-3.4.2.jar
 homepage: http://www.elastic.co/guide/en/logstash/current/index.html
 licenses:
 - Apache License (2.0)
@@ -183,8 +183,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project:
-rubygems_version: 2.6.13
+rubygems_version: 3.1.6
 signing_key:
 specification_version: 4
 summary: Receives events over HTTP or HTTPS