414 Request - URI Too Long

[Boon Chye Lau]

Hi,

I understand that the following error:

414 Request - URI Too Long

means that the url is too long.

Does anyone know what is the maximum length that the url
can go? I cannot find any information on the maximum
length from Microsoft KB.

Thanks,
Boon Chye

[doug]

Does this help?
http://support.microsoft.com/?id=208427

doug

>.
>

[Boon Chye]

This seems to be for IE. How about IIS 5.0? The error
seems to come from IIS 5.0? Any way to increase this limit?

Thanks,
Boon Chye

>.
>

[Terry Harney [MSFT]]

Here's the IIS article:

248061 Error Message: HTTP 414 - Request - URI Too Long
http://support.microsoft.com/default.aspx?scid=KB;EN-US;248061

Also see "How To Set Limits on the Size of the URL" - it's near the bottom
of this page:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/columns/i
nsider/iisi1001.asp

From the above technet link:

"By default, IIS does have a limit on the size of the URL plus the HTTP
header fields. In IIS 4.0 that limit is 2 MB. In IIS 5.0, the limit is 128
KB. Both of these values are quite large for general use and this threshold
can be lowered."

HTH,

Terry

Terry Harney [MSFT]

This posting is provided “AS IS” with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

--------------------
| Content-Class: urn:content-classes:message
| From: "Boon Chye" <lboo...@pacific.net.sg>
| Sender: "Boon Chye" <lboo...@pacific.net.sg>
| References: <0a9201c360ba$570206c0$a601...@phx.gbl>
<0ec801c360d2$ab8848e0$a301...@phx.gbl>
| Subject: 414 Request - URI Too Long
| Date: Tue, 12 Aug 2003 19:10:53 -0700
| Lines: 30
| Message-ID: <07d801c36140$1fac90b0$a401...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNhQB+sUlXKO8zsTtiXK6JF8Xl47A==
| Newsgroups: microsoft.public.inetserver.iis
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:270627
| NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
| X-Tomcat-NG: microsoft.public.inetserver.iis

[rahul kumar]

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.

http://net-informations.com/q/mis/len.html