<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
+1 for using POST (if it is easier to implement... Chris?)<div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 17.04.2021 05:11:17 schrieb Vanessa Freudenberg <vanessa@codefrau.net>:</p><div style='font-family:Arial,Helvetica,sans-serif'>
<div dir="ltr"><div>The argument to the server call is serializing the whole definition:</div><div><br></div>serializeForRequest: aMCDefinition <br> ^ ((ReferenceStream on: (RWBinaryOrTextStream on: ByteArray new)) nextPut: aMCDefinition ; yourself) contents asString encodeForHTTP<div><br></div><div>So either, as Levente suggests, it needs to be POSTed which allows larger data, or something smaller needs to be posted to the server, like MCDefinition>>description. Either way, it sounds like both server and client need to be touched for this.</div><div><br></div><div>–Vanessa–<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 16, 2021 at 4:17 PM Levente Uzonyi <<a href="mailto:leves@caesar.elte.hu">leves@caesar.elte.hu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The problem is that the service is implemented as a GET request instead <br>
of a POST or PUT request, so data can only be encoded in the URL.<br>
Like most web servers, nginx has an upper limit on the length of the URLs <br>
accepted (though it's implicit in case of nginx).<br>
And even though the accepted maximum length could be increased, there <br>
would still be cases where the error occurs.<br>
The right solution is to implement this as a POST or a PUT service.<br>
<br>
<br>
Levente<br>
<br>
On Fri, 16 Apr 2021, Christoph Thiede wrote:<br>
<br>
> Hmm ... Confusingly, the error message still persists when I manually<br>
> truncate the source in the method definition. On the other hand, the feature<br>
> works fine for other methods such as String >> #asInteger. Is the request<br>
> limit just way too low? Could you maybe increase this limitation?<br>
><br>
> Best,<br>
> Christoph<br>
><br>
><br>
><br>
> -----<br>
> Carpe Squeak!<br>
> --<br>
> Sent from: <a href="http://forum.world.st/Squeak-Dev-f45488.html" rel="noreferrer" target="_blank">http://forum.world.st/Squeak-Dev-f45488.html</a><br>
<br>
</blockquote></div></div>
</div></blockquote>
</div></body>