Data base connection error - 414 Request-URI Too long

[Djibril]

Hi,
I am getting the following DB connection error (when I trye to save the connection).

But there is no error when I just test it

This connection worked perfectly before.
Regards

[patrick]

When does this happen? Is something changed on the server?

The error is that the URI is too long, the allowed length depends on the server configuration and is normally around 2kB. It is also possible that there are some rewrites/redirects that are in a loop.

414 URI Too Long

The debug log could help us identify the problem.

How to report bugs together with the Wappler debug log

Updated for Wappler Version 1.1.0 and higher We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log. Starting from version 1.1.0 the logging isn’t available per default, so you need to restart Wappler with logging. You can do that by clicking on the Wappler’s tray icon (Windows right click) and then choose “Restart with Logging” Then reproduce your problem and choose to submit a bug report from the Wappler menu File / Submit error report ……

[Djibril]

Hi
My site folder (local) is on another computer in the network. I notice (maybe it’s a mistake) that the problem occurs when I refresh the connection from a computer on which the site folder is not located.
This is also the case when I save a file after modification from this computer. Some links that are in the file are automatically truncated.

[evanchitger]

@patrick

The HTTP 414 URI Too Long response status code

Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. Extremely long URLs are usually a mistake. If you keep URLs under 2000 characters , they’ll work in virtually any combination of client and server software. URI actually have a character limit depending on several things. Chrome limits url length of 2MB for practical reasons and to avoid causing denial-of-service problems in inter-process communication. On most platforms, Chrome’s omnibox limits URL display to 32kB ( kMaxURLDisplayChars ) although a 1kB limit is used on VR platforms. IE - 2083 characters, Firefox - 2047 characters, Safari 80000 characters and Opera 190,000 characters.

To resolve the problem :

• By POST request: Convert query string to json object and sent to API request with POST

• By GET request: Max length of request is depend on sever side as well as client side. Most webserver have limit 8k which is configurable. On the client side the different browser has different limit. The browser IE and Safari limit to 2k, Opera 4k and Firefox 8k. means the max length for the GET request is 8k and min request length is 2k.

If exceed the request max length then the request truncated outside the limit by web server or browser without any warning. Some server truncated request data but the some server reject it because of data lose and they will return with response code 414.