fix bug of dead loop when get http 4xx error from Elasticsearch

[wtfeng]

4xx error from Elasticsearch such as too big entity or incomplete message format will cause dead loop from the logback-elasticsearch-appender to Elasticsearch. It will also cause big network flow and cause a lot of money on cloud.

[agido-jrieks]

@wtfeng this repository here seems to be unmaintained... we maintain a fork and integrated you PR there:
agido-malter/logback-elasticsearch-appender#21

It will be include in version 3.0.9, which is currently being prepared. Thank you very much!

[abatkin]

@agido-jrieks would you be interested in helping maintain the "internetitem" logback-elasticsearch-appender? Or should I add something to the readme suggesting people go to your fork instead? Feel free to drop me an e-mail and we can chat (address is in my GitHub profile)

[wtfeng]

@wtfeng this repository here seems to be unmaintained... we maintain a fork and integrated you PR there: agido-malter/logback-elasticsearch-appender#21

It will be include in version 3.0.9, which is currently being prepared. Thank you very much!

That will be great. I will use your version in my project.