HttpLogShipper starts hammering target after a certain amount of errors about serilog-sinks-http

Thanks for the prompt reaction. We're good. We just told our clients to get their sh*t together ;-) The issue starts filling up the log files after 6 hours of having a wrong configuration, so most of the time people start noticing way before, that they are not getting any remote log messages. This one actually popped up on a test system, which nobody paid any real attention to, so nothing critical.

[github-actions]

Hi there and welcome to this repository!

A maintainer will be with you shortly, but first and foremost I would like to thank you for taking the time to report this issue. Quality is of the highest priority for us, and we would never release anything with known defects. We aim to do our best but unfortunately you are here because you encountered something we didn't expect. Lets see if we can figure out what went wrong and provide a remedy for it.

[FantasticFiasco]

Wow, this is a really nasty bug. Exactly the opposite of what one would like to happen.

I’ll look into this, are you able to work around the issue until it has been fixed?

[FantasticFiasco]

v5.2.1 has been published to nuget.org. Can you try it out, making sure we've fixed your issue?

Sorry, took a few days to get back to you. Our QA people let this run for more than two days with a broken config now and everything looks good. Retransmission attempts every 10 minutes, as expected. Thanks for the quick fix!

[FantasticFiasco]

Thanks for reporting it. Best of luck to you in the future!