The WASM networking code crashes on us. Especially in more complex setups (5.14 also did not work without modifications from my side):
does not correctly handle headers.
This code cannot work as headerData is accessed with i which can go twice as high as headerData.count()
I'm also not sure whether its save to define customHeaders like this, especially not in the context of emscripten, but I assume the headers need to be allocated somehow.
This code also looks dangerous and unlikely to reliably work. extraData is going out of scope, I'm not sure the constData pointer object will survive that, but it non-WASM environments this is very likely to crash.
Same here. Its not clear whether emscripten_fetch copies the provided url. If not this is likely to crash.
I would provide a fix, but currently we have a lot of remaining issues which are not fixed, by the above changes (except for a simple test case).