Horizon API: "transactions" function should have a parameter to skip XDR content

[alien2108]

What problem does your feature solve?

Some transactions (claimable balance....) have HUGE XDR load. Like 10Mb per transaction. If you do not need XDR info it would be good to provide parameter to skip this data in return. We have seen "transactions" responses that were 800MB for a single wallet due to complete overload of XDR fields.

What would you like to see?

Something as "xdr=true(default)/false" that would not return value of result_xdr and result_meta_xdr

What alternatives are there?

[Shaptic]

You're in luck: the SDF Horizon instance (which I presume you're using) will soon turn off ingestion of transaction metadata (see #5452). If you aren't using it, the SKIP_TXMETA flag does what you want!