QueryString loss when redirecting from arweave.net/txid?param1=foo to txid.arweave.net/txid

[dievardump]

It appears that the gateways, when redirecting to the unique subdomain, are not including the QueryString part of the URL

Query string are very useful for front-end applications:

• prefilling data in a form
• selecting data in javascript
• passing any arbitrary data to the code (which can be great for any tracking / behavior etc...)

QueryString is part of the URL RFC and there shouldn't be any reason to remove it when doing a redirection.

By removing it, the gateway is forcing people that need it to link to https://txId.arweave.net/txId/?foo=bar directly, which kind of breaks the idea of decentralization (we should be able to use ar://txId?foo=bar and not set any specific gateway) but also makes storing those URL way more expensive when stored on systems where every byte has a cost.

example

this link https://arweave.net/7nhx1ZjpG4xstYIxDQs6TITw30ntwOfcjP43txyxqXc?imageId=0

should redirect to https://5z4hdvmy5enyy3fvqiyq2cz2jscpbx2j5xaopxem7y33ohfrvf3q.arweave.net/7nhx1ZjpG4xstYIxDQs6TITw30ntwOfcjP43txyxqXc/?imageId=0

but only redirect to https://5z4hdvmy5enyy3fvqiyq2cz2jscpbx2j5xaopxem7y33ohfrvf3q.arweave.net/7nhx1ZjpG4xstYIxDQs6TITw30ntwOfcjP43txyxqXc/

which totally break the front-end since imageId is a parameter needed to select data in the JavaScript