Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / logstash-plugins/logstash-input-http issues and pull requests
#94 - SSL Issue - Unknown SSL protocol error in connection
Issue -
State: open - Opened by danielkasen over 6 years ago
- 2 comments
#93 - avoid creation of SSLContext for each connection
Pull Request -
State: closed - Opened by jsvd over 6 years ago
- 2 comments
Labels: performance-improvements
#92 - How can I use logstash-input-http 3.2.0 on logstash 6.x?
Issue -
State: closed - Opened by only-gale over 6 years ago
- 1 comment
#91 - after upgrade the plugin, the old http plugin still exist and not using new one
Issue -
State: closed - Opened by IzekChen over 6 years ago
- 2 comments
#90 - Respond with ElasticSearch response
Issue -
State: closed - Opened by ayZagen over 6 years ago
- 3 comments
#89 - option to reject malformed requests
Issue -
State: closed - Opened by jpcarey over 6 years ago
- 3 comments
Labels: enhancement, hacktoberfest
#88 - Setting password without username should raise an error
Issue -
State: open - Opened by jsvd almost 7 years ago
- 1 comment
Labels: bug, good first issue
#87 - Enforce content-type header parsing
Pull Request -
State: closed - Opened by ebuildy almost 7 years ago
- 2 comments
#86 - Support HTTP stream as used by journald-upload
Issue -
State: open - Opened by ThorbenJ almost 7 years ago
- 2 comments
Labels: enhancement
#85 - move most message handling code to java
Pull Request -
State: closed - Opened by jsvd almost 7 years ago
- 1 comment
Labels: performance-improvements, internal-cleanup
#84 - respond with correct http protocol version
Pull Request -
State: closed - Opened by jsvd almost 7 years ago
#83 - Access control for browsers stops working when basic auth is enabled
Issue -
State: open - Opened by pkoretic almost 7 years ago
- 14 comments
Labels: int-shortlist
#78 - Document possible server response codes
Issue -
State: closed - Opened by redbaron4 about 7 years ago
Labels: docs
#77 - Allow to configure keep-alive timeout
Issue -
State: open - Opened by vbohata about 7 years ago
- 2 comments
#76 - I have a problem with the logstash-input-http
Issue -
State: closed - Opened by Ccxlp about 7 years ago
- 27 comments
#68 - allow changing the default target field for host and headers data
Pull Request -
State: closed - Opened by jsvd over 7 years ago
- 1 comment
#67 - Add option to disable "ok" resonse
Issue -
State: closed - Opened by jakommo over 7 years ago
- 3 comments
Labels: enhancement, adoptme, hacktoberfest
#66 - resource overload when backend (eg elastic) unavailable
Issue -
State: closed - Opened by pputerla over 7 years ago
- 6 comments
#63 - Does password field work on http input?
Issue -
State: closed - Opened by paul42 almost 8 years ago
- 3 comments
#61 - Host field is unconditionally overwritten
Issue -
State: closed - Opened by magnusbaeck over 8 years ago
- 6 comments
#59 - Allow custom HTTP responses and message to be set in the config file
Pull Request -
State: closed - Opened by vinnyw over 8 years ago
- 10 comments
#58 - Add metrics for the http input
Pull Request -
State: closed - Opened by purbon over 8 years ago
- 3 comments
Labels: enhancement
#57 - Support boolean flag to retain HTTP headers
Issue -
State: closed - Opened by jmkgreen over 8 years ago
- 3 comments
#55 - verify_mode - "peer" vs. "force_peer"
Issue -
State: closed - Opened by simonclausen over 8 years ago
- 1 comment
#41 - Change field name.
Pull Request -
State: closed - Opened by yfhong about 9 years ago
- 3 comments
#35 - Support "Content-Type: application/json; charset=utf-8"
Issue -
State: closed - Opened by maximpashuk over 9 years ago
- 4 comments
Labels: enhancement
#34 - Cant send log from Application using http plugin
Issue -
State: closed - Opened by nowshad-amin over 9 years ago
- 1 comment
Labels: bug, unconfirmed, needs details
#13 - message is empty when encoding = chuncked
Issue -
State: closed - Opened by sander-su over 9 years ago
- 3 comments
Labels: bug
#10 - Should headers be saved by default in the `@metadata` field?
Issue -
State: closed - Opened by ph over 9 years ago
- 3 comments
Labels: enhancement