<div dir="ltr"><div dir="ltr">On Mon, Oct 7, 2019 at 4:41 PM Levente Uzonyi <<a href="mailto:leves@caesar.elte.hu">leves@caesar.elte.hu</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, 7 Oct 2019, Nicolas Cellier wrote:<br>
<br>
> Hi All,<br>
> when trying to browse revisions for some long methods (some VMMaker methods are long) this often lead to failure Notifier.<br>
> <br>
> Indeed, it seems like {self serializeForRequest: aMCDefinition} is serializing the whole method source...<br>
> <br>
> You might want to try with SistaRegisterAllocatingCogit>>genSpecialSelectorComparison<br>
> <br>
> Whole reply is:<br>
> <br>
> HTTP/1.1 414 Request-URI Too Large<br>
> server: nginx/1.16.0<br>
> date: Mon, 07 Oct 2019 20:55:41 GMT<br>
> content-type: text/html<br>
> content-length: 177<br>
> connection: close<br>
> <br>
> <html><br>
> <head><title>414 Request-URI Too Large</title></head><br>
> <body><br>
> <center><h1>414 Request-URI Too Large</h1></center><br>
> <hr><center>nginx/1.16.0</center><br>
> </body><br>
> </html><br>
> <br>
> Is this (URI length) something we can tune at server side?<br>
<br>
Yes, it could be tuned, but that wouldn't solve the problem. URIs should <br>
not be arbitrarily long.<br>
The proper solution would be to make the server expect POST requests with <br>
the content sent in the request body, and the image sending matching POST <br>
requests instead of GET request.<br>
<br>
Btw, we had a discussion about this issue, but nothing happened since <br>
then.<br></blockquote><div><br></div><div>It came up a couple of times this year. Some background and the method needing fixed, in case someone has time to do it.</div><div><br></div><div> <a href="http://lists.squeakfoundation.org/pipermail/squeak-dev/2019-July/202772.html">http://lists.squeakfoundation.org/pipermail/squeak-dev/2019-July/202772.html</a></div><div> </div></div></div>