Apache Error 414 Request Uri Too Large
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with
Nginx 414 Request Uri Too Large
us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack request uri too large ajax Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign
Request-uri Too Large Php
up How do I resolve a HTTP 414 “Request URI too long” error? up vote 51 down vote favorite 11 I have developed a PHP web app. I am giving an option to the user to update multiple issues on one go. request-uri too large the requested url's length exceeds the capacity limit for this server. In doing so, sometimes the user is encountering this error. Is there any way to increase the lenght of URL in apache? php apache http-status-codes share|improve this question edited May 23 '10 at 11:56 John Feminella 173k29272305 asked May 23 '10 at 11:50 JPro 1,64063571 If you're seeing this error on a Windows server and/or in an IIS / ASP.NET app, see question: stackoverflow.com/q/23237538/12484 –Jon Schneider Jan 6 at 16:59 add a comment| 4 Answers 4 active oldest votes up vote 96 apache limitrequestline down vote accepted 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. However, note that if you're actually running into this limit, you are probably abusing GET to begin with. You should use POST to transmit this sort of data -- especially since you even concede that you're using it to update values. If you check the link above, you'll notice that Apache even says "Under normal conditions, the value should not be changed from the default." share|improve this answer edited May 23 '10 at 12:01 answered May 23 '10 at 11:55 John Feminella 173k29272305 I tried using POST at first, but this is an update operation on the database, and I am refreshing the orginal page using the values that were originally posted to that page. –JPro May 23 '10 at 12:42 3 JPro: Updating a database is more or less the exact reason you would use POST. Nothing about using POST precludes you from populating the same form with the fields that were just posted, so I'm not sure what you mean by that. –John Feminella May 23 '10 at 12:45 @JPro: The usual technique in that case is to POST to the same page. The handler for the page (which can be the same code for both GET and POST) first checks for POST parameters, handles them if it finds t
guarantee providing any support for
414 Request Uri Too Long Ajax
it. Please be aware that this material is how to fix 414 request-uri too large provided for your information only and using it is done so
Http Error 414. The Request Url Is Too Long
at your own risk. Symptoms Requests with long URLs are being rejected by Apache with the following error message: Request-URI http://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error Too Large The requested URL's length exceeds the capacity limit for this server. Apache/2.2.3 (CentOS) Server at .... Port 443 Cause Apache limits the allowed size of a client's HTTP request-line (e.g.
PerlNews Q&A Tutorials Poetry RecentThreads NewestNodes Donate What'sNew on Aug 31, 2000 at 09:03UTC ( #30474=perlquestion: print w/replies, xml ) Need Help?? damian has asked for the wisdom of the Perl Monks concerning the following question: hi fella monks, i currently doing a program where in you can modify html document via web browser. http://www.perlmonks.org/?node_id=30474 i don't think this a bug in my code, 'coz the error is "414 Request-URI Too Large". I am passing the modified string with a post method and as a parameter in my perl code. had anyone here experienced one of this? oh btw i'm using apache web server.Comment on 414 Request-URI Too Large Replies are listed 'Best First'. (Ovid) Re: 414 Request-URI Too Large by Ovid (Cardinal) on Aug 31, 2000 at 09:53UTC There are a couple of conditions uri too that can cause this issue. One is a redirect URL prefix pointing to a suffix of itself. If you're doing any redirection, check for this. The other rare, but still more common, instance occurs when generating a get request which has too many characters for a geniune URL (typically 2048 to 4096 bytes). This means switching back to a post from a get. I see that you state that you are using a post method, so I would examine the uri too large raw HTTP headers to verify that your client isn't erroneously sending the request via the get method. Stranger things have been known to happen. Also, I don't know how to find this in Apache, but if you could find out the max length of requests and how to set this, it may help. CGI.pm can also throw an error if you exceed maximum post length, but I believe that it's just a simple die message and doesn't generate a 414. Probably generates a 5xx status code on the die. Cheers, Ovid[reply] RE: (Ovid) Re: 414 Request-URI Too Large by merlyn (Sage) on Aug 31, 2000 at 19:16UTC 414 means "URI is too large". Under Apache, this is a configurable limit, controlled by the LimitRequestLine configuration parameter. The maximum for this parameter appears to be 8190 by default, but even that can be hacked at compile time. The W3 specs do not provide a "minimum maximum" or a "maxiumum maximum" for the length of a URI, so you really are on your own to see what will work in any given situation. There's no theoretical reason why a 50 megabyte GET would be disallowed, so the common chatter of "you can't have a URI longer than mumbleK bytes" has no basis in reality, because the right answer is "well, it depends". -- Randal L. Schwartz, Perl hacker[reply] Re^3: 414 Request-URI Too Large by didierbdx (Initiate) on Aug 26, 2008