Prosody : http_file_share_size_limit of second virtualhost is displayed wrongly to default value(1024 kB)

[ecxod]

Let's admit we have a configuration like this using mod_http_file_share

VirtualHost "example.de"
...(unrelated things)...

VirtualHost "example2.org"
...(unrelated things)...

Component "share.example.de" "http_file_share"
	http_file_share_size_limit = 1024*1024*1024 --1 GB

Component "share.example2.org" "http_file_share"
	http_file_share_size_limit = 1024*1024*512 --512 MB

or using mod_http_upload

VirtualHost "example.de"
...(unrelated things)...

VirtualHost "example2.org"
...(unrelated things)...

Component "share.example.de" "http_upload"
	http_upload_file_size_limit= 1024*1024*1024 --1 GB

Component "share.example2.org" "http_upload"
	http_upload_file_size_limit= 1024*1024*512 --512 MB

in this case "http_file_share_size_limit" or "http_upload_file_size_limit" of share.example2.org is 512 MB

on conversations it is shown like 1024 KB, what is in fact the wrong value.
the funny part is that it also consequently does not let me upload :))

on gajim it is shown (more or less) correctly

[licaon-kter]

By any chance, example2.org and share.example2.org both have an identity type='file' in the disco response and both have a max-file-size? The one from example2.org is 1048576 (what Conversations sees)?

You've already asked in the Prosody channel?

/PS: as the Readme says, app repo has long move to https://codeberg.org/iNPUTmice/Conversations but we can continue this here.

[licaon-kter]

Moved to https://codeberg.org/iNPUTmice/Conversations/issues/295 ?