Handle OOM situations

[scaprile]

No description provided.

[cpq]

There is no change to mg_vprintf() in net.c - is that intentional ?

[scaprile]

There is no change to mg_vprintf() in net.c - is that intentional ?

That's already been merged after testing, since you suggested it I assumed you'd approve it.

mongoose/src/net.c

Lines 10 to 20 in b3b73f4

	size_t mg_vprintf(struct mg_connection *c, const char *fmt, va_list *ap) {
	size_t old = c->send.len;
	size_t expected = mg_vxprintf(mg_pfn_iobuf, &c->send, fmt, ap);
	size_t actual = c->send.len - old;
	if (actual != expected) {
	mg_error(c, "OOM");
	c->send.len = old;
	actual = 0;
	}
	return actual;
	}

[cpq]

@scaprile should we kill this PR ?

[scaprile]

@scaprile should we kill this PR ?

@cpq No, this PR handles everything else not printing, particularly lots of actions in TLS. Without this PR, we may send malformed TLS records or MQTT messages or even HTTP requests/responses under OOM conditions.
It is waiting for your review, it has been done in two stages.