logstash-input-http 3.3.0-java → 3.3.1-java

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 92e713ed58dc95fd484874bef08c957a1a22ec47a3f0dfeaf9dc7f14769e9049
4
- data.tar.gz: 36d6efc77e63323d295ac5a5dffd7357195cde8415851faed480b48534e49220
3
+ metadata.gz: eac357929f3d0d5b0529c8987c3298830a9355a19f75421776e81f78c0cf1bad
4
+ data.tar.gz: cf9c4141ace9c9749d61eb00bc37ea8dd1f576a2841c0a9466ee7517d1bddc3d
5
5
  SHA512:
6
- metadata.gz: c749f65f31e6ed9ca8c6502a66cdaec6b2dd9b739969104938043bbf764f017f107fef908b27de7e28683c217092ddda7219c4594480d7298fcfd0b5bcc78738
7
- data.tar.gz: 53adf0bc2ff98f28fccf0133db8221a3b02f8474a549d9b332e67f751773b080f350c8a479f3ac5a14308b45f390afaceb247583116de3a51a80c61609ffc215
6
+ metadata.gz: 8a45a91673381a8900534d99d048c7d3bc452ac751d957a277bb497a36dc67ab1e07dda18df0772236d7fbf638d440b5d842d1ec15fbf30dd03a14e1a5f4df97
7
+ data.tar.gz: 218ee19acc86f9043e894b9f8718a2ee507f0adee5d1cdc40110aed0d7013e78514a58c37400bad690b551373a6a492181749ab013cb52fed65c9f589896123f
data/CHANGELOG.md CHANGED
@@ -1,3 +1,7 @@
1
+ ## 3.3.1
2
+ - Added 201 to valid response codes [#114](https://github.com/logstash-plugins/logstash-input-http/issues/114)
3
+ - Documented response\_code option
4
+
1
5
  ## 3.3.0
2
6
  - Added configurable response code option [#103](https://github.com/logstash-plugins/logstash-input-http/pull/103)
3
7
  - Added explanation about operation order of codec and additional_codecs [#104](https://github.com/logstash-plugins/logstash-input-http/pull/104)
data/VERSION CHANGED
@@ -1 +1 @@
1
- 3.3.0
1
+ 3.3.1
data/docs/index.asciidoc CHANGED
@@ -77,6 +77,7 @@ This plugin supports the following configuration options plus the <<plugins-{typ
77
77
  | <<plugins-{type}s-{plugin}-port>> |<<number,number>>|No
78
78
  | <<plugins-{type}s-{plugin}-max_pending_requests>> |<<number,number>>|No
79
79
  | <<plugins-{type}s-{plugin}-response_headers>> |<<hash,hash>>|No
80
+ | <<plugins-{type}s-{plugin}-response_code>> |<<number,number>>, one of `[200, 201, 202, 204]`|No
80
81
  | <<plugins-{type}s-{plugin}-ssl>> |<<boolean,boolean>>|No
81
82
  | <<plugins-{type}s-{plugin}-ssl_certificate>> |a valid filesystem path|No
82
83
  | <<plugins-{type}s-{plugin}-ssl_certificate_authorities>> |<<array,array>>|No
@@ -183,6 +184,19 @@ so it should be changed very carefully as it can lead to memory pressure and imp
183
184
  If you need to deal both periodic or unforeseen spikes in incoming requests consider enabling the
184
185
  Persistent Queue for the logstash pipeline.
185
186
 
187
+ [id="plugins-{type}s-{plugin}-response_code"]
188
+ ===== `response_code`
189
+
190
+ * Value can be any of: 200, 201, 202, 204
191
+ * Default value is `200`
192
+
193
+ The HTTP return code if the request is processed successfully.
194
+
195
+ Other return codes may happen in the case of an error condition, such as
196
+ invalid credentials (401), internal errors (503) or backpressure (429).
197
+
198
+ If 204 (No Content) is set, the response body will not be sent in the response.
199
+
186
200
  [id="plugins-{type}s-{plugin}-response_headers"]
187
201
  ===== `response_headers`
188
202
 
@@ -4,4 +4,4 @@ require 'jar_dependencies'
4
4
  require_jar('io.netty', 'netty-all', '4.1.30.Final')
5
5
  require_jar('io.netty', 'netty-tcnative-boringssl-static', '2.0.12.Final')
6
6
  require_jar('org.apache.logging.log4j', 'log4j-api', '2.11.1')
7
- require_jar('org.logstash.plugins.input.http', 'logstash-input-http', '3.3.0')
7
+ require_jar('org.logstash.plugins.input.http', 'logstash-input-http', '3.3.1')
@@ -115,7 +115,7 @@ class LogStash::Inputs::Http < LogStash::Inputs::Base
115
115
 
116
116
  config :max_content_length, :validate => :number, :required => false, :default => 100 * 1024 * 1024
117
117
 
118
- config :response_code, :validate => [200, 202, 204], :default => 200
118
+ config :response_code, :validate => [200, 201, 202, 204], :default => 200
119
119
  # Deprecated options
120
120
 
121
121
  # The JKS keystore to validate the client's certificates
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: logstash-input-http
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.3.0
4
+ version: 3.3.1
5
5
  platform: java
6
6
  authors:
7
7
  - Elastic
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2019-02-04 00:00:00.000000000 Z
11
+ date: 2019-12-03 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  requirement: !ruby/object:Gem::Requirement
@@ -147,7 +147,7 @@ files:
147
147
  - vendor/jar-dependencies/io/netty/netty-all/4.1.30.Final/netty-all-4.1.30.Final.jar
148
148
  - vendor/jar-dependencies/io/netty/netty-tcnative-boringssl-static/2.0.12.Final/netty-tcnative-boringssl-static-2.0.12.Final.jar
149
149
  - vendor/jar-dependencies/org/apache/logging/log4j/log4j-api/2.11.1/log4j-api-2.11.1.jar
150
- - vendor/jar-dependencies/org/logstash/plugins/input/http/logstash-input-http/3.3.0/logstash-input-http-3.3.0.jar
150
+ - vendor/jar-dependencies/org/logstash/plugins/input/http/logstash-input-http/3.3.1/logstash-input-http-3.3.1.jar
151
151
  homepage: http://www.elastic.co/guide/en/logstash/current/index.html
152
152
  licenses:
153
153
  - Apache License (2.0)