logstash-input-http
logstash-input-http copied to clipboard
logstash-plugins
Keepalive option at https://github.com/logstash-plugins/logstash-input-http/blob/master/src/main/java/org/logstash/plugins/inputs/http/NettyHttpServer.java#L57 should not be hardcoded, but it must respect "Connection" header. If in plugin configuration user provides custom response header as ``` response_headers => {"Connection" => "close"}...
Starting the plugin with `input { http { password => 'hello'} }` will not enable auth and also raise no warning or error that both username and password are needed...
Using bouncy castle it's possible to support both pkcs#1 and pkcs#8 keys. Example implementation in https://github.com/logstash-plugins/logstash-input-tcp/pull/124/files#diff-708e5e3c9eea0d86f843e0944d528f59R72
Using version 6.4.0 I can't get SSL to work properly. The input comes up and listens on the port, but when I try to hit it I get `Unknown SSL...
In the latest release of puma to 2.16 we have found a regression in the code because one of the option concerning verification of client certificate was not correctly configured....
This is an ask from the Elastic Cloud Monitoring team, in order to enable Logstash output for our [Elastic Serverless Forwarder](https://github.com/elastic/elastic-serverless-forwarder) product. https://github.com/elastic/elastic-serverless-forwarder/issues/112. Based on discussions we have had already...
Add a new logstash configuration parameter to avoid adding header metadata and ```event.original``` to events Closes https://github.com/logstash-plugins/logstash-input-http/issues/157
This is my config: ``` input { http { port => 8080 ssl_enabled => true ssl_key => "/etc/logstash/certs/logstash/logstash.pkcs8.key" ssl_certificate => "/etc/logstash/certs/logstash/logstash.crt" ssl_certificate_authorities => ["/etc/logstash/certs/ca/ca.crt"] ssl_client_authentication => required } } ```...
According to the documentation (https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http.html#plugins-inputs-http-ecs_metadata), the following ECS metadata is populated by the http input plugin: - Host IP address - Complete HTTP headers - HTTP version - client user...
