10 ms·
Using Go standard HTTP libraries doesn't guarantee things are stable. Here's an example how a missing option (that is Go 1.8+ - which is a recent release) can
by drdaeman 10y ago
Using Go standard HTTP libraries doesn't guarantee things are stable.
Here's an example how a missing option (that is Go 1.8+ - which is a recent release) can lead to a DoS: https://github.com/containous/traefik/issues/1322 https://github.com/containous/traefik/issues/1322
- andmarios 10y agoYeah, as it happens in software in general there aren't any guarantees. I could too give you a link to heartbleed. Caddy wasn't affected.
- drdaeman 10y agoWell, yes, although security and stability are different matters. Every software has bugs, I just said that the fact something is using Go HTTP library doesn't automagically mean it's production quality. There are always many ways to accidentally shot oneself in the leg. (Caddy, in my experience is production quality. I've used it in a few projects and haven't had any serious issues. Maybe that's just my use cases, though.)
- omginternets 10y agoStability is relative. Knowing that it uses standard Go networking libs is an indication of how stable this thing is.