It appears there is a 256 character limit for web projects in Xojo 2020r2.1. Any longer and we get a status 414 error and the HandleURL event does not fire.
A simple request in Xojo 2019r3.2 of 400 characters works fine.
Is there a way around this?
Regards,
Lee
What exactly are you doing? Should you be using a different type of request?
We are updating some legacy code which used GET parameters to use POST, BUT there is a requirement to handle old and new requests. The URLs can be anything up to about 300 characters, but MAY be longer. Works fine in Xojo 2019r3.2, which we are updating from.
Regards,
Lee
If there’s a requirement to handle the old requests you should create a feedback ticket with an example project. I’m not sure of a way to work around the framework behavior. I was only going to suggest and help determine a more appropriate request.
I just wanted to confirm that there is a limit in Xojo 2020r2.1 and that it has reduced from 2048(ish) characters to 256 now.
This is obviously a complete pain to work around. Several days development time wasted.
Regards,
Lee
do you connect to the same web server? maybe a security config thing there.
HTTP 414 “Request URI too long” <- found in web
https://www.w3schools.com/tags/ref_httpmethods.asp
url max should be 2k
Yes. We control both ends. The requester and handler. Older web services (built with Xojo 2019r3.2) used both GET and POST, but we can migrate newer versions to just use POST.
The limit appeared to be 2K before Web 2.0, but now appears to be 256 characters. We never used that many before, but it looks like sometimes the GET parameters can be more than 256 characters.
So far for us, Web 2.0 (and API 2.0) has given us nothing but a development headache. It has provided us no new functionality and we’ve had to update a huge amount of code, just to stay the same (Arrays, String, Events)
<https://xojo.com/issue/63299>
Regards,
Lee
The feedback report has been updated to show that there is now a 256 character URL limit in Xojo 2020r2.1
The URL lenght limit is not visible on our web 2.0 servers. We hosted a few of them and testing a URL with over 6983 characters didn’t even give a error.
How did you deploy this server? behind Apache, Nginx trough a load balancer (digital ocean?) or just plain or Xojo Cloud?
It seems DO doesn’t give any issue whatsoever with very long URL’s.
Could it be that you mean the BODY payload instead of the URL ?
This is just a self contained web executable so it handles the URLs itself. Just calling a simple URL longer than 256 characters means the HandleURL event does not fire and returns a status 414 error.
Judging by the feedback report, the limit may be extended in a later version.
Lee
So it means it is the build in web server componet in xojo web app.
Yes, the server is built as a standalone executable in Xojo.