Abort Http Error 414 Request-uri Too Large
Contents |
by: [ date ] [ thread ] [ subject ] 414 request-uri too long [ author ] On 10-03-2010 03:22, Jesus Cea wrote:
414 Request-uri Too Large Nginx
> Trying to clone the Python mercurial mirror I have an error: > > """ request-uri too long php > [jcea at babylon5 home]$ hg clone http://hg.python.org/cpython/ > destination directory: cpython > requesting all changes > abort: HTTP Error 414: Request-URI Too
Http Error 414. The Request Url Is Too Long
Large > """ > > Using an sniffer, I see the request is actually huge. I am using > Mercurial 1.5. > > I can pull individual branches, with "-b" flag > (http://hg.python.org/cpython/branches), but I have the same issue doing > a "pull" later. > > It request-uri too large the requested url's length exceeds the capacity limit for this server. is not possible to download the full repository?. I could update the > clone branch by branch, but must be a better way... > > Seems to be a bug... Sometimes Mercurial's http wire protocol sends rather large request URIs, which can sometime overflow the buffer the web server has set aside for these things, which will then abort the request. In some cases the limit is configurable on the web server. I don't know why the request would be that large for a full clone, though, where no discovery (of what changesets we are missing locally) should happen. /Sune Previous message: abort: HTTP Error 414: Request-URI Too Large Next message: abort: HTTP Error 414: Request-URI Too Large Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the Mercurial mailing list
a free Git and Mercurial client for Windows. Atlassian SourceTree is a free Git and Mercurial client for Mac. Bitbucket
How To Fix 414 Request-uri Too Large
Public Issue Tracker master Issues Issues Issue #1895 resolved hg clone/push/pull
414 Request Uri Too Long Ajax
fails with HTTP Error 414: Request-URI Too Large mediawiki created an issue 2010-05-10 We have a 414 request-uri too large php large repository with over 300 heads (http://bitbucket.org/mediawiki/root). However, due to http://mercurial.selenic.com/bts/issue2126 anyway to clone/pull this repository fails. It is difficult to fix this bug without changing the https://www.mercurial-scm.org/pipermail/mercurial/2010-March/030556.html wire protocol, but maybe the HTTP server URL length limit can be pushed to accommodate large multi-head repositories? hg Comments (6) Jesper Noehr changed status to open I've adjusted the buffer size from 4k to 32k, should have plenty of space to hold the request now. Also, I've adjusted the max POST body from https://bitbucket.org/site/master/issues/1895/hg-clone-push-pull-fails-with-http-error 100M to 2G. Let me know if this has fixed it. 2010-05-10T11:51:41+00:00 mediawiki reporter attached hg Unfortunately, still getting 414. Looks like the HTTP request (including IP and TCP headers) is around 10K, so it should fit the new limit. Attached is a tcpdump of the TCP conversation. 2010-05-10T12:02:15+00:00 Anonymous I get the same thing when I attempt $ hg clone http://bitbucket.org/mirror/liftweb requesting all changes abort: HTTP Error 414: Request-URI Too Large If I do hg clone -r tip http://butbucket.org/mirrow/liftweb it works, but subsequent hg incoming, hg pull etc then get: $ hg pull pulling from http://bitbucket.org/mirror/liftweb searching for changes abort: HTTP Error 500: Internal Server Error I can do hg incoming -r tip but it's not optimal. 2010-05-20T02:49:51+00:00 Jesper Noehr Anon, can you reproduce? 2010-05-21T12:45:57+00:00 Jesper Noehr changed status to resolved 2010-12-14T06:30:13+00:00 Zach Davis staff removed component Removing component: wireprotocol (automated comment) 2014-02-21T19:22:10+00:00 Log in to comment Assignee Jesper Noehr Type bug Priority major Status resolved Component – Vot
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 http://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation http://www.checkupdown.com/status/E414.html Tags Users Badges Ask Question x Dismiss Join the Stack 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 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 uri too app. I am giving an option to the user to update multiple issues on one go. 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,63563571 If you're seeing this error on a Windows server and/or in an 414 request-uri too 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 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. &
large i.e. too many bytes. Typically Web servers set fairly generous limits on length for genuine URLs e.g. up to 2048 or 4096 characters. If your URL is particularly long, you can usually try shorter variations to see roughly where the limit is. If your long URL is indeed valid, then the Web server may need to be reconfigured to allow your URLs through. Understand that Web servers have to set some reasonable limit here, because they have to deal with badly programmed clients trying to give them huge garbage URLs. Fixing 414 errors - general This error seldom occurs in most Web traffic, particularly when the client system is a Web browser. The URLs in this case are typically standard hyperlinks found on Web pages. These links tend to be too large if they are simply wrong i.e. the Web page containing the link has been badly coded. If your client system is not a Web browser, the problem can only be resolved by examining what the client is trying to do then discussing with your ISP why the Web server rejects the size of the URL sent by the client system. Fixing 414 errors - CheckUpDown Our service monitors your site for HTTP errors like 414. This error should simply never occur on your CheckUpDown account. If it does, it typically indicates defective programming of our systems or of the Web server which manages the site. The length of the URL we send in the HTTP data stream is typically relatively small and well within the limits of what most Web servers should accept. You can test this for yourself by simply keying the URL into any Web browser. Please contact us (email preferred) whenever you encounter 414 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of the Web server software to agree the exact reason for the error. 414 errors in the HTTP cycle Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server: Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). Open an IP socket connection to that IP address. Write an HTTP data stream through that socket. Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. This error occurs in the final step above when the client receives an HTTP status code that it recognises as '414'. Our company also owns these other Web sites: A simple guide