The problem is that the service is implemented as a GET request instead 
of a POST or PUT request, so data can only be encoded in the URL.
Like most web servers, nginx has an upper limit on the length of the URLs 
accepted (though it's implicit in case of nginx).
And even though the accepted maximum length could be increased, there 
would still be cases where the error occurs.
The right solution is to implement this as a POST or a PUT service.


Levente

On Fri, 16 Apr 2021, Christoph Thiede wrote:

> Hmm ... Confusingly, the error message still persists when I manually
> truncate the source in the method definition. On the other hand, the feature
> works fine for other methods such as String >> #asInteger. Is the request
> limit just way too low? Could you maybe increase this limitation?
>
> Best,
> Christoph
>
>
>
> -----
> Carpe Squeak!
> --
> Sent from: http://forum.world.st/Squeak-Dev-f45488.html