Http Error 414 Request-uri Too Large Mercurial
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 Large 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 how to fix 414 request-uri too large 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 Public Issue Tracker master Issues Issues Issue #1895 resolved
414 Request-uri Too Large Solution
hg clone/push/pull fails with HTTP Error 414: Request-URI Too Large mediawiki created request-uri too large the requested url's length exceeds the capacity limit for this server. an issue 2010-05-10 We have a large repository with over 300 heads (http://bitbucket.org/mediawiki/root). However, due to http://mercurial.selenic.com/bts/issue2126 anyway to
The Remote Server Returned An Error 414 Request Uri Too Long
clone/pull this repository fails. It is difficult to fix this bug without changing the wire protocol, but maybe the HTTP server URL length limit can be pushed to accommodate large multi-head repositories? https://www.mercurial-scm.org/pipermail/mercurial/2010-March/030556.html 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 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 https://bitbucket.org/site/master/issues/1895/hg-clone-push-pull-fails-with-http-error 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 – Votes 0 Watchers 4 Blog Support Plans & pricing Documentation API Site status Version info Terms of service Privacy policy English Git 2.7.4.1.g5468f9e Mercurial 3.6.3 Django 1.7.11 Python 2.7.3 564c96d1f0f9 / 564c96d1f0f9 @ app-106 JIRA Software Confluence Bamboo SourceTree HipChat Atlassian Help Online help Learn Git Keyboard shortcuts Latest features Bitbucket tutorials Site status Support
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 us Stack http://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack http://mercurial.selenic.narkive.com/pWYBne8Q/solve-and-understand-http-error-414-request-uri-too-large 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 app. I am giving an option to the user to update multiple issues on one go. In doing so, sometimes the uri too 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 175k29272305 asked May 23 '10 at 11:50 JPro 1,74563673 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 down vote accepted Under Apache, the limit request-uri too large 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 175k29272305 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 them, then returns the page with the proper values filled in, which will be eith
occurs regularly on ourproject.We develop new features in their own branches and some colleagues don'tclose them.If someone in our team doesn't pull often, he will get the error "HTTPError 414: Request-URI Too Large".We raised the limits on our web server, but I want to understand why thisproblem exists.How does mercurial generate the URLs for a pull-Request? Why does this urlbecome longer and longer over time?And is there a way to solve this problem instead of raising the limits onserver side?Currently we just pull the important branches to "solve" the problem. Butthat's just a workaround.I'm looking forward your help and explanations.Regards,Daniel Siepmann. Mads Kiilerich 2014-08-26 16:43:25 UTC PermalinkRaw Message Post by Daniel SiepmannHello everyone,the error "HTTP Error 414: Request-URI Too Large" occurs regularly onour project.We develop new features in their own branches and some colleaguesdon't close them.If someone in our team doesn't pull often, he will get the error "HTTPError 414: Request-URI Too Large".We raised the limits on our web server, but I want to understand whythis problem exists.How does mercurial generate the URLs for a pull-Request? Why does thisurl become longer and longer over time?And is there a way to solve this problem instead of raising the limitson server side?Currently we just pull the important branches to "solve" the problem.But that's just a workaround.http://selenic.com/hg/rev/510cafe72004 is another workaround for thebad use of Mercurial - it will make the request half as big./Mads Steve Barnes 2014-08-26 17:59:45 UTC PermalinkRaw Message Post by Mads KiilerichPost by Daniel SiepmannHello everyone,the error "HTTP Error 414: Request-URI Too Large" occurs regularly onour project.We develop new features in their own branches and some colleaguesdon't close them.If someone in our team doesn't pull often, he will get the error"HTTP Error 414: Request-URI Too Large".We raised the limits on our web server, but I want to understand whythis problem exists.How does mercurial generate the URLs for a pull-Request? Why doesthis url become longer and longer o