I notice you list a known issue of 64k limit on Request_Content. You might find the limit is in the use of Evaluate. I've run into problems using Evaluate with @UrlEncode where certain XML message sizes would truncate unexpectedly. In practice, Request_Content should hold unlimited text (as you upload files through this same header). You might replace your Evaluate @Explode with Split and see if that resolves the problem.
Hey Jake,
I notice you list a known issue of 64k limit on Request_Content. You might find the limit is in the use of Evaluate. I've run into problems using Evaluate with @UrlEncode where certain XML message sizes would truncate unexpectedly. In practice, Request_Content should hold unlimited text (as you upload files through this same header). You might replace your Evaluate @Explode with Split and see if that resolves the problem.
Script replacements for @URLEncode / Decode:
{Link}
@ReplaceSubstring can be replaced with Join(Split(.....
The speed on the script might be a bit (teeny weeny bit) slower than Evaluate, but your limit should disappear.
Nice work as usual!