Support "Content-Type: application/json; charset=utf-8" about logstash-input-http HOT 4 CLOSED

Faced same issue, but there is an easy workaround to overcome it. In logstash configuration file specify codec=> json and it should work smoothly.

from logstash-input-http.

Encountered the same bug this week - not easy to chase down and broke my QA environment for a day.

https://github.com/logstash-plugins/logstash-input-http/blob/master/lib/logstash/inputs/http.rb#L154

Is this not easily addressed by parsing out the Content-Type into type/subtype and removing any subsequent parameters? Perhaps the correct fallback sequence with regard to the entries in additional_codecs should be

• exact match on "type/subtype; parameter[; parameter]*"
• match on "type/subtype"
• default to "plain"

from logstash-input-http.

yes this should be possible with https://netty.io/4.1/api/io/netty/handler/codec/http/HttpUtil.html#getMimeType-io.netty.handler.codec.http.HttpMessage-:

"content-type: text/html; charset=utf-8" - "text/html" will be returned 
"content-type: text/html" - "text/html" will be returned 
"content-type: empty header - null we be returned

Something like master...ebuildy:patch-1

from logstash-input-http.

solved by #87

from logstash-input-http.