Upload file with TLS

[jbbcst]

Hi,

We are currently testing the integration of Mongoose 7.14 in our project. For uploading files we have used the example of
mongoose/examples/file-transfer/upload. When we upload a file of size 7,864 KB without TLS, it's work fine, below are some of the logs when the upload ends:

[2024-06-10 16:32:38.480]  [debug] 1d5ad18 4 mongoose.c:7907:mg_mgr_poll   1 -- tchrc 0 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad18 4 mongoose.c:7907:mg_mgr_poll   2 r- tchrc 0 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad18 4 mongoose.c:7455:recv_raw      2 2048 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad18 3 mongoose.c:7502:read_conn     2 6 0:0:0 2048 err 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad18 4 mongoose.c:7907:mg_mgr_poll   1 -- tchrc 0 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad18 4 mongoose.c:7907:mg_mgr_poll   2 r- tchrc 0 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad19 4 mongoose.c:7455:recv_raw      2 463 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad19 3 mongoose.c:7502:read_conn     2 6 0:0:0 463 err 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad19 4 mongoose.c:7907:mg_mgr_poll   1 -- tchrc 0 0
[2024-06-10 16:32:38.480]  [debug] 1d5ad19 4 mongoose.c:7907:mg_mgr_poll   2 -w tchrc 0 0
[2024-06-10 16:32:38.481]  [debug] 1d5ad19 4 mongoose.c:7333:mg_io_send    2 80 0
[2024-06-10 16:32:38.481]  [debug] 1d5ad19 3 mongoose.c:7513:write_conn    2 6 snd 80/2048 rcv 0/2048 n=80 err=0
[2024-06-10 16:32:38.481]  [debug] 1d5ad1a 4 mongoose.c:7907:mg_mgr_poll   1 -- tchrc 0 0
[2024-06-10 16:32:38.982]  [debug] 1d5af0e 4 mongoose.c:7907:mg_mgr_poll   2 -- tchrc 0 0

When we do the same with TLS, we have got an error, below are some of the logs when the upload ends:

[2024-06-10 16:39:45.235]  [debug] 1dc3023 4 mongoose.c:7907:mg_mgr_poll   11 -- Tchrc 0 0
[2024-06-10 16:39:45.235]  [debug] 1dc3023 4 mongoose.c:7907:mg_mgr_poll   1 -- Tchrc 0 0
[2024-06-10 16:39:45.235]  [debug] 1dc3023 4 mongoose.c:7907:mg_mgr_poll   13 r- Tchrc 10240 3139584
[2024-06-10 16:39:45.268]  [debug] 1dc3044 4 mongoose.c:7455:recv_raw      13 2048 0
[2024-06-10 16:39:45.268]  [debug] 1dc3045 3 mongoose.c:7502:read_conn     13 6 0:0:3141632 2048 err 0
[2024-06-10 16:39:45.269]  [debug] 1dc3045 4 mongoose.c:7907:mg_mgr_poll   11 -- Tchrc 0 0
[2024-06-10 16:39:45.269]  [debug] 1dc3045 4 mongoose.c:7907:mg_mgr_poll   1 -- Tchrc 0 0
[2024-06-10 16:39:45.269]  [debug] 1dc3045 4 mongoose.c:7907:mg_mgr_poll   13 r- Tchrc 8192 3141632
[2024-06-10 16:39:45.297]  [debug] 1dc3061 4 mongoose.c:7455:recv_raw      13 2048 0
[2024-06-10 16:39:45.297]  [debug] 1dc3061 3 mongoose.c:7502:read_conn     13 6 0:0:3143680 2048 err 0
[2024-06-10 16:39:45.297]  [debug] 1dc3061 4 mongoose.c:7907:mg_mgr_poll   11 -- Tchrc 0 0
[2024-06-10 16:39:45.297]  [debug] 1dc3062 4 mongoose.c:7907:mg_mgr_poll   1 -- Tchrc 0 0
[2024-06-10 16:39:45.297]  [debug] 1dc3062 4 mongoose.c:7907:mg_mgr_poll   13 r- Tchrc 6144 3143680
[2024-06-10 16:39:45.325]  [debug] 1dc307d 4 mongoose.c:7455:recv_raw      13 2048 0
[2024-06-10 16:39:45.325]  [debug] 1dc307d 3 mongoose.c:7502:read_conn     13 6 0:0:3145728 2048 err 0
[2024-06-10 16:39:45.325]  [debug] 1dc307e 4 mongoose.c:7907:mg_mgr_poll   11 -- Tchrc 0 0
[2024-06-10 16:39:45.325]  [debug] 1dc307e 4 mongoose.c:7907:mg_mgr_poll   1 -- Tchrc 0 0
[2024-06-10 16:39:45.326]  [debug] 1dc307e 4 mongoose.c:7907:mg_mgr_poll   13 r- Tchrc 4096 3145728
[2024-06-10 16:39:45.326]  [debug] 1dc307e 1 mongoose.c:1363:mg_error      13 6 MG_MAX_RECV_SIZE

what can be done to avoid this?

[scaprile]

What you refer to, is a demo on how to deal with several issues. The upload process is described in this tutorial https://mongoose.ws/documentation/tutorials/http/file-uploads/
The example as is does not have provisions to deal with TLS, so probably what you did, when you modified our code, is not correct or does not apply for that scenario
MG_MAX_RECV_SIZE

mongoose/mongoose.c

Lines 7493 to 7504 in 6cb1c3c

	static bool ioalloc(struct mg_connection *c, struct mg_iobuf *io) {
	bool res = false;
	if (io->len >= MG_MAX_RECV_SIZE) {
	mg_error(c, "MG_MAX_RECV_SIZE");
	} else if (io->size <= io->len &&
	!mg_iobuf_resize(io, io->size + MG_IO_SIZE)) {
	mg_error(c, "OOM");
	} else {
	res = true;
	}
	return res;
	}

Internal buffers are being exhausted due to some reason I can't pinpoint because you modified our code to fit your purpose.
If you read our docs, https://mongoose.ws/documentation/#build-options , you'll see

MG_MAX_RECV_SIZE (3 * 1024 * 1024) Maximum recv buffer size

where 3 * 1024 * 1024 = 3145728, or 3MiB
The obvious quick and dirty action is to change that value if you can afford the extra memory.
The other simple thing, if you don't expect to deal with all the issues shown there, is to "just do it" as shown in the main example code for the already mentioned tutorial , and use the HTTP server example code https://github.com/cesanta/mongoose/tree/master/tutorials/http/http-server
What I suggest you should do, is read our docs and tutorials:
https://mongoose.ws/documentation/#user-guide
https://mongoose.ws/documentation/tutorials/error-handling/
and determine what is the best way for you to integrate Mongoose.

Then, if there is an actual issue, please open an issue, honor the issue template so we can know your scenario and reproduce the issue if necessary, and let us know exactly what you are doing

[jbbcst]

Thank you for your reply.