Webassembly: mutlithread application crashes upon webserver 304 reply

When launcing a multithreaded WASM application, the worker.js should be loaded 4 times (depending on threading settings). We have experienced, that in a situation, when the browser have to check the worker.js (like cache aging) and the server responds 304 (file is unchanged), the worker.js file is loaded with 0 size.

Although it might be a browser issue, the error is not handled at all from Qt side, but the application crashes with different stacks.